Methods and apparatus for determining a clinician&#39;s intent to order an item

ABSTRACT

Techniques for determining a clinician&#39;s intent to order an item may include processing a free-form narration, of an encounter with a patient, narrated by a clinician, using a natural language understanding engine implemented by one or more processors, to extract at least one clinical fact corresponding to a mention of an orderable item from the free-form narration. The processing may comprise distinguishing between whether the at least one clinical fact indicates an intent to order the orderable item or does not indicate an intent to order the orderable item. In response to determining that the at least one clinical fact indicates an intent to order the orderable item, an order may be generated for the orderable item.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit under 35 U.S.C. § 120 as a continuation of U.S. patent application Ser. No. 13/782,048, filed Mar. 1, 2013, titled “Methods and Apparatus for Determining a Clinician's Intent to Order an Item,” now U.S. Pat. No. 10,032,127, which claims the benefit under 35 U.S.C. § 120 as a continuation-in-part of U.S. patent application Ser. No. 13/030,974, filed Feb. 18, 2011, titled “Methods and Apparatus for Analyzing Specificity in Clinical Documentation,” now U.S. Pat. No. 8,799,021, which is incorporated herein by reference in its entirety.

BACKGROUND 1. Field

The techniques described herein are directed generally to the field of medical documentation, and more particularly to techniques for the creation and use of patient records in medical settings.

2. Description of the Related Art

Medical documentation is an important process in the healthcare industry. Most healthcare institutions maintain a longitudinal medical record (e.g., spanning multiple observations or treatments over time) for each of their patients, documenting, for example, the patient's history, encounters with clinical staff within the institution, treatment received, and/or plans for future treatment. Such documentation facilitates maintaining continuity of care for the patient across multiple encounters with various clinicians over time. In addition, when an institution's medical records for large numbers of patients are considered in the aggregate, the information contained therein can be useful for educating clinicians as to treatment efficacy and best practices, for internal auditing within the institution, for quality assurance, etc.

Historically, each patient's medical record was maintained as a physical paper folder, often referred to as a “medical chart”, or “chart”. Each patient's chart would include a stack of paper reports, such as intake forms, history and immunization records, laboratory results and clinicians' notes. Following an encounter with the patient, such as an office visit, a hospital round or a surgical procedure, the clinician conducting the encounter would provide a narrative note about the encounter to be included in the patient's chart. Such a note could include, for example, a description of the reason(s) for the patient encounter, an account of any vital signs, test results and/or other clinical data collected during the encounter, one or more diagnoses determined by the clinician from the encounter, and a description of a plan for further treatment. Often, the clinician would verbally dictate the note into an audio recording device or a telephone giving access to such a recording device, to spare the clinician the time it would take to prepare the note in written form. Later, a medical transcriptionist would listen to the audio recording and transcribe it into a text document, which would be inserted on a piece of paper into the patient's chart for later reference.

Currently, many healthcare institutions are transitioning or have transitioned from paper documentation to electronic medical record systems, in which patients' longitudinal medical information is stored in a data repository in electronic form. Besides the significant physical space savings afforded by the replacement of paper record-keeping with electronic storage methods, the use of electronic medical records also provides beneficial time savings and other opportunities to clinicians and other healthcare personnel. For example, when updating a patient's electronic medical record to reflect a current patient encounter, a clinician need only document the new information obtained from the encounter, and need not spend time entering unchanged information such as the patient's age, gender, medical history, etc. Electronic medical records can also be shared, accessed and updated by multiple different personnel from local and remote locations through suitable user interfaces and network connections, eliminating the need to retrieve and deliver paper files from a crowded file room.

SUMMARY

One embodiment is directed to a method comprising: processing a free-form narration, of an encounter with a patient, narrated by a clinician, using a natural language understanding engine implemented by one or more processors, to extract at least one clinical fact corresponding to a mention of an orderable item from the free-form narration, wherein the processing comprises distinguishing between whether the at least one clinical fact indicates an intent to order the orderable item or does not indicate an intent to order the orderable item; and in response to determining that the at least one clinical fact indicates an intent to order the orderable item, generating an order for the orderable item.

Another embodiment is directed to apparatus comprising at least one processor, and at least one processor-readable storage medium storing processor-executable instructions that, when executed by the at least one processor, cause the at least one processor to perform a method comprising: processing a free-form narration, of an encounter with a patient, narrated by a clinician, using natural language understanding, to extract at least one clinical fact corresponding to a mention of an orderable item from the free-form narration, wherein the processing comprises distinguishing between whether the at least one clinical fact indicates an intent to order the orderable item or does not indicate an intent to order the orderable item; and in response to determining that the at least one clinical fact indicates an intent to order the orderable item, generating an order for the orderable item.

Another embodiment is directed to at least one computer-readable storage medium encoded with computer-executable instructions that, when executed, perform a method comprising: processing a free-form narration, of an encounter with a patient, narrated by a clinician, using natural language understanding, to extract at least one clinical fact corresponding to a mention of an orderable item from the free-form narration, wherein the processing comprises distinguishing between whether the at least one clinical fact indicates an intent to order the orderable item or does not indicate an intent to order the orderable item; and in response to determining that the at least one clinical fact indicates an intent to order the orderable item, generating an order for the orderable item.

Another embodiment is directed to a method comprising: receiving an original text that is a representation of a narration of a patient encounter provided by a clinician; re-formatting the original text, using at least one processor, to produce a formatted text; extracting one or more clinical facts from the formatted text, wherein a first fact of the one or more clinical facts is extracted from a first portion of the formatted text, wherein the first portion of the formatted text is a formatted version of a first portion of the original text; and maintaining a linkage between the first fact and the first portion of the original text.

Another embodiment is directed to apparatus comprising at least one processor, and a memory storing processor-executable instructions that, when executed by the at least one processor, perform a method comprising: receiving an original text that is a representation of a narration of a patient encounter provided by a clinician; re-formatting the original text to produce a formatted text; extracting one or more clinical facts from the formatted text, wherein a first fact of the one or more clinical facts is extracted from a first portion of the formatted text, wherein the first portion of the formatted text is a formatted version of a first portion of the original text; and maintaining a linkage between the first fact and the first portion of the original text.

Another embodiment is directed to at least one computer-readable storage medium encoded with a plurality of computer-executable instructions that, when executed, perform a method comprising: receiving an original text that is a representation of a narration of a patient encounter provided by a clinician; re-formatting the original text to produce a formatted text; extracting one or more clinical facts from the formatted text, wherein a first fact of the one or more clinical facts is extracted from a first portion of the formatted text, wherein the first portion of the formatted text is a formatted version of a first portion of the original text; and maintaining a linkage between the first fact and the first portion of the original text.

Another embodiment is directed to a method comprising: extracting, using at least one processor, a plurality of clinical facts from a free-form narration of a patient encounter provided by a clinician, wherein the plurality of clinical facts comprises a first fact and a second fact, wherein the first fact is extracted from a first portion of the free-form narration, and wherein the second fact is extracted from a second portion of the free-form narration; and providing to a user a first indicator that indicates a first linkage between the first fact and the first portion of the free-form narration, and a second indicator, different from the first indicator, that indicates a second linkage between the second fact and the second portion of the free-form narration.

Another embodiment is directed to apparatus comprising at least one processor, and a memory storing processor-executable instructions that, when executed by the at least one processor, perform a method comprising: extracting a plurality of clinical facts from a free-form narration of a patient encounter provided by a clinician, wherein the plurality of clinical facts comprises a first fact and a second fact, wherein the first fact is extracted from a first portion of the free-form narration, and wherein the second fact is extracted from a second portion of the free-form narration; and providing to a user a first indicator that indicates a first linkage between the first fact and the first portion of the free-form narration, and a second indicator, different from the first indicator, that indicates a second linkage between the second fact and the second portion of the free-form narration.

Another embodiment is directed to at least one computer-readable storage medium encoded with a plurality of computer-executable instructions that, when executed, perform a method comprising: extracting a plurality of clinical facts from a free-form narration of a patient encounter provided by a clinician, wherein the plurality of clinical facts comprises a first fact and a second fact, wherein the first fact is extracted from a first portion of the free-form narration, and wherein the second fact is extracted from a second portion of the free-form narration; and providing to a user a first indicator that indicates a first linkage between the first fact and the first portion of the free-form narration, and a second indicator, different from the first indicator, that indicates a second linkage between the second fact and the second portion of the free-form narration.

Another embodiment is directed to a method comprising: collecting a set of one or more clinical facts from a clinician's encounter with a patient; determining from the set of facts, using at least one processor, that an additional fact that provides additional specificity to the set of facts may possibly be ascertained from the patient encounter; and alerting a user that the additional fact may possibly be ascertained from the patient encounter.

Another embodiment is directed to apparatus comprising at least one processor, and a memory storing processor-executable instructions that, when executed by the at least one processor, perform a method comprising: collecting a set of one or more clinical facts from a clinician's encounter with a patient; determining from the set of facts that an additional fact that provides additional specificity to the set of facts may possibly be ascertained from the patient encounter; and alerting a user that the additional fact may possibly be ascertained from the patient encounter.

Another embodiment is directed to at least one computer-readable storage medium encoded with a plurality of computer-executable instructions that, when executed, perform a method comprising: collecting a set of one or more clinical facts from a clinician's encounter with a patient; determining from the set of facts that an additional fact that provides additional specificity to the set of facts may possibly be ascertained from the patient encounter; and alerting a user that the additional fact may possibly be ascertained from the patient encounter.

Another embodiment is directed to a method comprising: collecting a set of one or more clinical facts from a clinician's encounter with a patient; determining, using at least one processor, that an unspecified diagnosis not included in the set of facts may possibly be ascertained from the patient encounter; and alerting a user that the unspecified diagnosis may possibly be ascertained from the patient encounter.

Another embodiment is directed to apparatus comprising at least one processor, and a memory storing processor-executable instructions that, when executed by the at least one processor, perform a method comprising: collecting a set of one or more clinical facts from a clinician's encounter with a patient; determining that an unspecified diagnosis not included in the set of facts may possibly be ascertained from the patient encounter; and alerting a user that the unspecified diagnosis may possibly be ascertained from the patient encounter.

Another embodiment is directed to at least one computer-readable storage medium encoded with a plurality of computer-executable instructions that, when executed, perform a method comprising: collecting a set of one or more clinical facts from a clinician's encounter with a patient; determining that an unspecified diagnosis not included in the set of facts may possibly be ascertained from the patient encounter; and alerting a user that the unspecified diagnosis may possibly be ascertained from the patient encounter.

Another embodiment is directed to a method comprising: determining, based on a free-form narration of a patient encounter provided by a clinician, that one or more clinical facts could possibly be ascertained from the patient encounter; providing to a user one or more options corresponding to the one or more clinical facts; receiving from the user a selection of a first option of the one or more options, the first option corresponding to a first fact of the one or more clinical facts; and updating a textual representation of the free-form narration, using at least one processor, to identify the first fact as having been ascertained from the patient encounter.

Another embodiment is directed to apparatus comprising at least one processor, and a memory storing processor-executable instructions that, when executed by the at least one processor, perform a method comprising: determining, based on a free-form narration of a patient encounter provided by a clinician, that one or more clinical facts could possibly be ascertained from the patient encounter; providing to a user one or more options corresponding to the one or more clinical facts; receiving from the user a selection of a first option of the one or more options, the first option corresponding to a first fact of the one or more clinical facts; and updating a textual representation of the free-form narration to identify the first fact as having been ascertained from the patient encounter.

Another embodiment is directed to at least one computer-readable storage medium encoded with a plurality of computer-executable instructions that, when executed, perform a method comprising: determining, based on a free-form narration of a patient encounter provided by a clinician, that one or more clinical facts could possibly be ascertained from the patient encounter; providing to a user one or more options corresponding to the one or more clinical facts; receiving from the user a selection of a first option of the one or more options, the first option corresponding to a first fact of the one or more clinical facts; and updating a textual representation of the free-form narration to identify the first fact as having been ascertained from the patient encounter.

BRIEF DESCRIPTION OF DRAWINGS

The accompanying drawings are not intended to be drawn to scale. In the drawings, each identical or nearly identical component that is illustrated in various figures is represented by a like numeral. For purposes of clarity, not every component may be labeled in every drawing. In the drawings:

FIG. 1 is a block diagram of an exemplary operating environment for a system in accordance with some embodiments of the present invention;

FIG. 2 is a screenshot illustrating an exemplary graphical user interface for a medical fact review system in accordance with some embodiments of the present invention;

FIGS. 3A and 3B are screenshots illustrating an exemplary display of medical facts in a user interface in accordance with some embodiments of the present invention;

FIG. 4 is a screenshot illustrating an exemplary display of linkage between text and a clinical fact in accordance with some embodiments of the present invention;

FIG. 5 is a screenshot illustrating an exemplary interface for entering a clinical fact in accordance with some embodiments of the present invention;

FIG. 6 is a flowchart illustrating an exemplary method for extracting one or more clinical facts corresponding to an orderable item, determining an intent to order, and generating an order for the orderable item in accordance with some embodiments of the present invention;

FIG. 7 is a block diagram of an illustrative system for processing a free-form narration, generating an order from it and providing the order to a fulfillment system in accordance with some embodiments of the present invention;

FIG. 8 is a screenshot illustrating an illustrative display of a generated order that a user may authorize or cancel in accordance with some embodiments of the present invention;

FIG. 9 is a flowchart illustrating an exemplary method for formatting text for clinical fact extraction in accordance with some embodiments of the present invention;

FIG. 10 is a flowchart illustrating an exemplary method for linking extracted clinical facts to text in accordance with some embodiments of the present invention;

FIG. 11 is a flowchart illustrating an exemplary method for analyzing specificity in accordance with some embodiments of the present invention;

FIG. 12 is a flowchart illustrating an exemplary method for identifying an unspecified diagnosis in accordance with some embodiments of the present invention;

FIG. 13 is a flowchart illustrating an exemplary method for updating text in accordance with some embodiments of the present invention; and

FIG. 14 is a block diagram of an exemplary computer system on which aspects of the present invention may be implemented.

DETAILED DESCRIPTION

An Electronic Health Record (EHR) is an electronic medical record that generally is maintained by a specific healthcare institution and contains data documenting the care that a specific patient has received from that institution over time. Typically, an EHR is maintained as a structured data representation, such as a database with structured fields. Each piece of information stored in such an EHR is typically represented as a discrete (e.g., separate) data item occupying a field of the EHR database. For example, a 55-year old male patient named John Doe may have an EHR database record with “John Doe” stored in the patient_name field, “55” stored in the patient_age field, and “Male” stored in the patient_gender field. Data items or fields in such an EHR are structured in the sense that only a certain limited set of valid inputs is allowed for each field. For example, the patient_name field may require an alphabetic string as input, and may have a maximum length limit; the patient_age field may require a string of three numerals, and the leading numeral may have to be “0” or “1”; the patient_gender field may only allow one of two inputs, “Male” and “Female”; a patient_birth_date field may require input in a “MM/DD/YYYY” format; etc.

Typical EHRs are also structured in terms of the vocabulary they use, as medical terms are normalized to a standard set of terms utilized by the institution maintaining the EHR. The standard set of terms may be specific to the institution, or may be a more widely used standard. For example, a clinician dictating or writing a free-form note may use any of a number of different terms for the condition of a patient currently suffering from an interruption of blood supply to the heart, including “heart attack”, “acute myocardial infarction”, “acute MI” and “AMI”. To facilitate interoperability of EHR data between various departments and users in the institution, and/or to allow identical conditions to be identified as such across patient records for data analysis, a typical EHR may use only one standardized term to represent each individual medical concept. For example, “acute myocardial infarction” may be the standard term stored in the EHR for every case of a heart attack occurring at the time of a clinical encounter. Some EHRs may represent medical terms in a data format corresponding to a coding standard, such as the International Classification of Disease (ICD) standard. For example, “acute myocardial infarction” may be represented in an EHR as “ICD-9 410”, where 410 is the code number for “acute myocardial infarction” according to the ninth edition of the ICD standard.

To allow clinicians and other healthcare personnel to enter medical documentation data directly into an EHR in its discrete structured data format, many EHRs are accessed through user interfaces that make extensive use of point-and-click input methods. While some data items, such as the patient's name, may require input in (structured) textual or numeric form, many data items can be input simply through the use of a mouse or other pointing input device (e.g., a touch screen) to make selections from pre-set options in drop-down menus and/or sets of checkboxes and/or radio buttons or the like.

The inventors have recognized, however, that while some clinicians may appreciate the ability to directly enter structured data into an EHR through a point-and-click interface, many clinicians may prefer being unconstrained in what they can say and in what terms they can use in a free-form note, and many may be reluctant to take the time to learn where all the boxes and buttons are and what they all mean in an EHR user interface. In addition, many clinicians may prefer to take advantage of the time savings that can be gained by providing notes through verbal dictation, as speech can often be a faster form of data communication than typing or clicking through forms.

Accordingly, some embodiments described herein relate to techniques for enhancing the creation and use of structured electronic medical records, using techniques that enable a clinician to provide input and observations via a free-form narrative clinician's note. Some embodiments involve the automatic extraction of discrete medical facts (e.g., clinical facts), such as could be stored as discrete structured data items in an electronic medical record, from a clinician's free-form narration of a patient encounter. In this manner, free-form input may be provided, but the advantages of storage, maintenance and accessing of medical documentation data in electronic forms may be maintained. For example, the storage of a patient's medical documentation data as a collection of discrete structured data items may provide the benefits of being able to query for individual data items of interest, and being able to assemble arbitrary subsets of the patient's data items into new reports, orders, invoices, etc., in an automated and efficient manner.

Automatic extraction of medical facts (e.g., clinical facts) from a free-form narration may be performed in any suitable way using any suitable technique(s), as aspects of the present invention are not limited in this respect. In some embodiments, pre-processing may be performed on a free-form narration prior to performing automatic fact extraction, to determine the sequence of words represented by the free-form narration. Such pre-processing may also be performed in any suitable way using any suitable technique(s), as aspects of the present invention are not limited in this respect. For example, in some embodiments, the clinician may provide the free-form narration directly in textual form (e.g., using a keyboard or other text entry device), and the textual free-form narration may be automatically parsed to determine its sequence of words. In other embodiments, the clinician may provide the free-form narration in audio form as a spoken dictation, and an audio recording of the clinician's spoken dictation may be received and/or stored. The audio input may be processed in any suitable way prior to or in the process of performing fact extraction, as aspects of the invention are not limited in this respect. In some embodiments, the audio input may be processed to form a textual representation, and fact extraction may be performed on the textual representation. Such processing to produce a textual representation may be performed in any suitable way. For example, in some embodiments, the audio recording may be transcribed by a human transcriptionist, while in other embodiments, automatic speech recognition (ASR) may be performed on the audio recording to obtain a textual representation of the free-form narration provided via the clinician's dictation. Any suitable automatic speech recognition technique may be used, as aspects of the present invention are not limited in this respect. In other embodiments, speech-to-text conversion of the clinician's audio dictation may not be required, as a technique that does not involve processing the audio to produce a textual representation may be used to determine what was spoken. In one example, the sequence of words that was spoken may be determined directly from the audio recording, e.g., by comparing the audio recording to stored waveform templates to determine the sequence of words. In other examples, the clinician's speech may not be recognized as words, but may be recognized in another form such as a sequence or collection of abstract concepts. It should be appreciated that the words and/or concepts represented in the clinician's free-form narration may be represented and/or stored as data in any suitable form, including forms other than a textual representation, as aspects of the present invention are not limited in this respect.

In some embodiments, one or more medical facts (e.g., clinical facts) may be automatically extracted from the free-form narration (in audio or textual form) or from a pre-processed data representation of the free-form narration using a fact extraction component applying natural language understanding techniques. In some embodiments, the medical facts to be extracted may be defined by a set of fact categories (also referred to herein as “fact types” or “entity types”) commonly used by clinicians in documenting patient encounters. In some embodiments, a suitable set of fact categories may be defined by any of various known healthcare standards. For example, in some embodiments, the medical facts to be extracted may include facts that are required to be documented by Meaningful Use standards promulgated by the U.S. government, e.g., under 42 C.F.R. § 495, which sets forth “Objectives” specifying items of medical information to be recorded for medical patients. Such facts currently required by the Meaningful Use standards include social history facts, allergy facts, diagnostic test result facts, medication facts, problem facts, procedure facts, and vital sign facts. However, these are merely exemplary, as aspects of the invention are not limited to any particular set of fact categories. Some embodiments may not use one or more of the above-listed fact categories, and some embodiments may use any other suitable fact categories. Other non-limiting examples of suitable categories of medical facts include findings, disorders, body sites, medical devices, subdivided categories such as observable findings and measurable findings, etc. The fact extraction component may be implemented in any suitable form, as aspects of the present invention are not limited in this respect. Exemplary implementations for a fact extraction component are described in detail below.

The inventors have recognized and appreciated that the automatic extraction of medical facts (e.g., clinical facts) directly from a free-form narration of a patient encounter provided by a clinician may create the opportunity for numerous enhancements to processes involved in medical documentation in healthcare institutions. Some such enhancements may help make it possible for a clinician to efficiently oversee a process involving deriving any one or combination of updated patient records, billing information, ordering information, quality of care assurances, decision support, etc., directly from a free-form narration in a single interactive session with a medical fact review system.

In some embodiments, automatic extraction of clinical facts from a textual representation of a clinician's free-form narration (e.g., from a text narrative) of a patient encounter may be enhanced by re-formatting the text narrative to facilitate the automatic extraction of the clinical facts. For example, in some embodiments a fact extraction component that performs the automatic fact extraction may make use of linguistic knowledge that has some dependency on accurate placement of sentence boundaries in the text narrative. Accordingly, in some embodiments, the fact extraction may be enhanced by adding, removing and/or correcting sentence boundaries in the text narrative to comply with the linguistic structure expected by the fact extraction component. Examples of ways in which sentence boundary pre-processing can be implemented are described below. In another example, automatic fact extraction may be enhanced by normalizing section headings in the text narrative to comply with standard section headings used by the healthcare institution for which the clinical documentation is being performed.

In some embodiments, a linkage may be maintained between each extracted clinical fact and the portion of the free-form narration from which that fact was extracted. For example, if a fact corresponding to “acute myocardial infarction” is extracted from a free-form narration because it included the term “heart attack”, a linkage may be maintained between that extracted fact and the words “heart attack” in the free-form narration. In some embodiments, while the clinician or another user is reviewing the extracted clinical facts via a user interface to a fact review system, the system may provide one or more indicators to the user (who may be the clinician himself or a different person) of the different linkages between the different extracted facts and the portions of the free-form narration from which they were extracted. Such indicators may be visual indicators, audio indicators, or any other suitable type of indicators, as aspects of the present invention are not limited in this respect. In some embodiments, such linkage indicators may enhance the ability of the clinician or other user to review the extracted facts for accuracy, with reference to the specific parts of the free-form narration that generated them. In some embodiments, if a textual representation of the free-form narration has been re-formatted prior to fact extraction, linkages may still be maintained between the extracted facts and the original text narrative, to allow the user to relate the extracted facts to the narration as it was originally given by the clinician. While some embodiments provide linkage information for each extracted fact, it should be appreciated that aspects of the invention relating to providing linkage information are not so limited, as linkage information may be provided for one or any subset of the extracted facts.

In some embodiments, automatically extracted clinical facts may also be automatically reviewed, and automatic alerts may be provided to the clinician or other user if opportunities are identified for the clinical documentation of the patient encounter to be improved. Such alerts may be visual alerts, audio alerts, or any other suitable type of alerts, as aspects of the present invention are not limited in this respect. In some embodiments, such alerts may be provided to the clinician or other user at a time subsequent to the completion of the patient encounter, and may provide the opportunity for the clinician or other user to provide additional information that was ascertained from the patient encounter but was not originally specified in the free-form narration. In other embodiments, such alerts may be provided to the clinician while the patient encounter is still in progress, and may provide the opportunity for the clinician to initiate further interaction with the patient to ascertain additional information to include in the clinical documentation.

In some embodiments, a fact review system may be programmed with a set of deterministic rules to trigger alerts. For example, a set of deterministic rules may specify that certain extracted facts, certain combinations of extracted facts, certain combinations of extracted facts and terms in the free-form narration, and/or certain combinations of facts extracted from the current patient encounter and facts from the patient's previous history automatically trigger alerts to the user. In other embodiments, the fact review system may be programmed to undertake a probabilistic analysis or apply a statistical model to determine whether information specified in the free-form narration will trigger alerts to the user. It should be appreciated, however, that a fact review system in accordance with embodiments described herein is not limited to any particular programming technique, as any suitable such technique may be used. In addition, it should be appreciated that automatic alerts may also be provided in embodiments that do not involve automatic extraction of clinical facts from a free-form narration. For example, such alerts may also be triggered by clinical facts received as discrete structured data items, such as direct input to an electronic medical record such as an EHR. It should thus be appreciated that alerts may be provided based on analysis of clinical facts collected in any suitable way, as aspects of the present invention are not limited in this respect.

In some embodiments, an alert may be provided when a set of one or more clinical facts is collected from a patient encounter, and it is determined that there is an opportunity to increase the specificity of the set of facts. In some embodiments, it may be determined that an additional fact may possibly be ascertained from the patient encounter, and that the additional fact would add specificity to the set of clinical facts already collected from the patient encounter. In one example, such an additional fact may be a more specific version of one of the original facts, and the specificity of the set of facts may be increased by replacing the original fact with its more specific version, provided that it can truly be ascertained from the patient encounter. For instance, the original fact may describe a condition, and the more specific version may describe the same condition as “acute” or “chronic”. In another example, two or more of the original facts, when appearing in combination, may imply an additional fact, and documenting the additional fact may increase the specificity of the record of the patient encounter. In some embodiments, an alert may query the user as to whether an additional fact should actually be ascertained from the patient encounter, and may allow the user to increase the specificity of the facts by documenting the additional fact.

In some embodiments, an alert may be provided when a set of one or more clinical facts is collected from a patient encounter, and it is determined that a diagnosis that was not specified in the set of facts may possibly be ascertained from the patient encounter. In one example, such an unspecified diagnosis may be a known comorbidity of a diagnosis that was included in the set of facts. In another example, the unspecified diagnosis may be a known complication of a procedure or diagnosis included in the set of facts. In yet another example, the unspecified diagnosis may be an identification of the fact that a diagnosis included in the set of facts is actually a complication of a procedure or other diagnosis included in the set of facts, or of a procedure or other diagnosis included in facts from the patient's history prior to the current encounter. Similarly, the unspecified diagnosis may be an identification of the fact that a diagnosis included in facts from the patient's previous history is a complication of a diagnosis ascertained during the current patient encounter. In some embodiments, when the possibility or likelihood of such an unspecified diagnosis is determined from the original set of facts collected from the patient encounter, an alert may query the user (e.g., the clinician or another user) as to whether the unspecified diagnosis should be ascertained from the patient encounter.

In some embodiments, an alert may be provided when a set of one or more clinical facts is collected from a patient encounter, and it is determined that two or more of the facts in the set conflict with each other in some way, or it is determined that one or more of the facts in the set conflict with one or more facts in the patient's history. In some embodiments, a fact review system may be programmed to automatically generate such alerts based on a known set of combinations of facts that have undesirable interactions. For example, an alert may be generated when the set of facts indicate that the patient has been prescribed a certain medication (drug A) in addition to a certain other medication (drug B) with which it negatively interacts, such that the two medications should not be prescribed together. In some embodiments, the prescriptions of both drug A and drug B may be specified in the set of facts collected from the current patient encounter, while in other embodiments, the prescription of drug A may be specified in a fact from the current patient encounter, and the prescription of drug B may be specified in a fact contained in a record of the patient's history with the institution. Thus, in some embodiments, the fact review system may access both facts collected from a current patient encounter and facts from the patient's historical records to determine whether alerts should be generated. In some embodiments, an alert to a conflict may be triggered by a combination of facts, at least one of which does not correspond to a medication. For example, alerts may be provided for contraindications related to a combination of a medication with an allergy, a medication with a diagnosis, a medication with a patient's age or gender, a medication with a condition indicated in the patient's history, a medical procedure with any of the foregoing characteristics, or any other combination of a planned treatment with another clinical fact from the current patient encounter or from the patient's history for which the planned treatment is known to be contraindicated.

In some embodiments, an alert may be provided when a set of one or more clinical facts is collected from a patient encounter, and it is determined that there is an opportunity to add to the clinical documentation of the patient encounter for quality review purposes. In some embodiments, a fact review system may be programmed with a set of deterministic rules to generate automatic alerts in response to certain facts or certain combinations of facts, based on a standard set of quality of care measures. Such a quality of care standard may be proprietary and unique to the specific healthcare institution or may be a standard that is not institution specific, such as that of the Physician Quality Reporting Initiative (PQRI) or that of the Joint Commission on Accreditation of Healthcare Organizations (JCAHO). Any suitable quality of care standard may be used, as aspects of the present invention are not limited to any particular quality of care standard. In some embodiments, when a collected fact or combination of facts is associated with a certain recommended action on the part of the clinician according to the quality of care standard, an alert may be provided to query the user as to whether the recommended action was performed.

In some embodiments, a mechanism may be provided to adaptively filter the automatic alerts generated by the fact review system, by learning from the clinician's or other user's interaction with the system over time. For example, if it is determined that a particular user consistently ignores a particular type of alert, the system may stop issuing similar alerts when they are triggered by future facts. In some embodiments, the adaptive learning may be specific to each individual user and may help to prevent alert fatigue, which may involve frustration at repeatedly being bothered by an alert that the user does not find relevant. In some embodiments, the adaptive learning may involve the collection of data regarding patterns of facts that tend to be present when the user ignores alerts, and the system may filter out future alerts that match those patterns of facts. In some embodiments, adaptive alert filtering may be performed based on rules or statistical usage patterns on an institutional level, such that alerts not considered relevant for the specific healthcare institution in which the fact review system is operating are not provided.

In some embodiments, a human user other than the clinician may review the set of clinical facts collected from a patient encounter, and may manually (e.g., not automatically, but involving human action) cause one or more alerts to be issued to the clinician that were not issued automatically by the fact review system. Such a human user may manually cause alerts to be issued in any suitable way, as aspects of the invention are not limited in this respect. In one example, the human user may provide instructional input to the fact review system to cause the fact review system to generate an alert specified by the human user. In other examples, the human user may use a different method and/or system, other than the fact review system, to issue an alert to the clinician. Such a different method in some embodiments need not be machine-based, as aspects of the invention are not limited in this respect. In some embodiments, the human user may have access to the patient's past medical history within and/or external to the healthcare institution, for example in the form of an electronic medical record and/or past clinical documents relating to the patient's care at the institution and/or elsewhere. In some embodiments, the human user may make reference to this past medical history, in addition to the clinical facts from the current patient encounter, to determine whether to manually cause an alert to be issued to the clinician. In some embodiments, the human user may determine to issue an alert, similar to any of the various types of automatic alerts described above, if the facts and the patient's history indicate a situation in which the automatic fact review system should have generated an automatic alert, but it failed to accurately recognized the situation. In some embodiments, if the clinician chose to ignore an alert automatically generated by the fact review system, but ignoring such an alert was contrary to the policy of the institution, the human reviewer may determine to manually issue a follow-up alert to the clinician. Thus, in some embodiments, an automatic fact review system may coexist in an institutional setting with a manual review process involving a human user, and the manual review process may provide back-up and/or additional functionality to complement the automatic fact review processes.

In some embodiments, when medical facts are extracted from a free-form narration, a fact extraction component may encounter situations in which disambiguation is desired between multiple facts that could potentially be extracted from the same portion of the free-form narration. In one example, a term in the free-form narration might be linked to two different concepts in a formal ontology (described below) used by the fact extraction component, and it might not be likely that both of those concepts were intended to coexist in the free-form narration. In another example, the fact extraction component may apply a statistical model (examples of which are described below) to identify facts to be extracted from a certain portion of text, and the statistical model may come up with multiple alternative hypotheses for a single fact to be extracted. In some embodiments, the statistical model may be used to score the alternative hypotheses based on probability, confidence, or any other suitable measure of an estimated likelihood that each alternative accurately represents an intended semantic meaning of the portion of text from which it is to be extracted. In such situations, a fact review system in some embodiments may provide an interface to receive user input to disambiguate between multiple facts tentatively extracted by the fact extraction component. Such a user interface can be in any suitable form, as aspects of the invention are not limited in this respect. In one non-limiting example, the fact review system may present to the user a certain number of the alternative hypotheses having high estimated likelihood scores. In some embodiments, each of the options provided may correspond to one of the multiple tentative facts, and the user may choose one of the options to specify which fact should actually be extracted from the free-form narration.

In some cases, when the user makes a selection of a fact presented through a structured choice provided by the fact review system, the set of facts extracted by the fact extraction component may be updated accordingly, but the original free-form narration from which the facts were extracted may remain unchanged. In some embodiments, in other cases, a textual representation of the clinician's free-form narration may automatically be updated (e.g., changed) to explicitly identify the user's selected fact as having been ascertained from the patient encounter. For example, if the free-form narration originally included a term linked to two different concepts in the fact extraction component's ontology, the fact review system could present the user a structured choice between a different term linked only to one of the concepts and a different term linked only to the other of the concepts. When the user selects one of the different terms in the structured choice presented, in some embodiments the text narrative may automatically be updated to replace the original term with the selected term. In another example, if application of a statistical fact extraction model resulted in multiple alternative hypotheses for a fact to be extracted from a certain portion of the free-form narration, the fact review system could present the user a choice between at least two of the alternative hypotheses (e.g., the N alternative hypotheses having the highest scores). In some cases in some embodiments, the text narrative may automatically be updated to better reflect the alternative hypothesis selected by the user. For example, if the original text narrative included the term “asthma,” the fact extraction component might present alternative fact hypotheses of “chronic obstructive asthma” and “asthma unspecified.” If the user then selects the “chronic obstructive asthma” hypothesis (representing a more specific asthma fact), the text narrative could then automatically be updated to replace the original “asthma” term with “chronic obstructive asthma.” In some embodiments, such updating of the text narrative may be performed in response to any type of user selection of an option provided by the fact review system, corresponding to a medical fact that could possibly be ascertained from the patient encounter. Some examples include disambiguating options, options corresponding to additional facts for increased specificity and options corresponding to unspecified diagnoses, as discussed above. In some embodiments, rather than replacing text in the narrative, new text corresponding to the selected fact may be generated and simply added to the narrative in one or more appropriate locations. In some embodiments, the location(s) at which to insert text identifying the selected fact may be automatically determined by identifying one or more section headings in the text narrative, and by inserting the text in the section or sections most closely corresponding to the selected fact.

In some embodiments, a fact review system may allow a clinician or other user to directly add a clinical fact as a discrete structured data item, and to indicate a linkage to a portion of the clinician's free-form narration of the patient encounter from which the added fact should have been extracted. For example, the user may specify a clinical fact as a discrete structured data element, select a word or set of words (which need not be contiguous) in the free-form narration, and indicate that the specified fact is ascertained from that portion (e.g., that word or set of words) of the free-form narration. In some embodiments, when such a fact is added, the fact extraction component may be updated for that user (or for the clinician who provided the free-form narration), e.g., to link the selected word(s) from the free-form narration to one or more concepts in a formal ontology corresponding to the added fact, or to re-train a statistical fact extraction model to associate the selected word(s) with the added fact. In some embodiments, the free-form narration may further be re-processed by the updated fact extraction component to extract any further additional facts that may be determined based on the updated terminology. In one example, if the user selected a word in the patient history section of the free-form narration, and added a fact specifying that the patient has a history of a particular condition, the updated fact extraction component re-processing the free-form narration might identify the same word in the family history section, and extract an additional fact that the patient has a family history of the same condition. In some embodiments, such automatic re-processing may spare the clinician or other user the time and effort that otherwise would be required to define multiple facts corresponding to the same terminology in the free-form narration. In some embodiments, similar re-processing may be performed when the user edits or deletes a fact originally extracted automatically from the free-form narration, when the fact is linked to terminology that appears in multiple parts of the free-form narration.

In some embodiments, as discussed above, a fact review system may allow a user to add, delete and/or modify (collectively referred to as “change”) a medical fact extracted from a free-form narration of a patient encounter provided by a clinician, resulting in a change to the set of extracted facts. For example, in some embodiments, a user may add a fact to the set of extracted facts, e.g., by specifying a portion of the free-form narration and specifying a particular fact that should be extracted from that portion of the narration. In some embodiments, a user may specify an added fact directly, e.g., by typing, speaking, or otherwise inputting the particular fact to be added, or by selecting the fact and/or components of the fact from menu options. Alternatively or additionally, as described above, in some embodiments the system may present the user with a choice between multiple alternative hypotheses for a fact to be extracted from a portion of the free-form narration, and the user may select one of the presented hypotheses to add that fact to the set of extracted facts. In another example, a user may modify a fact already automatically extracted from the free-form narration, e.g., by selecting the extracted fact and inputting a different fact with which it should be replaced, or by selecting a component of the extracted fact and inputting a change to that component, etc. In another example, a user may delete an extracted fact, e.g., by selecting the extracted fact and selecting a “delete” option, or otherwise indicating that that fact should not have been extracted from the corresponding portion of the free-form narration. It should be appreciated, however, that the foregoing are merely examples, and a user may be allowed to add, delete and/or modify one or more facts in a set of extracted medical facts in any suitable way, as aspects of the invention are not limited in this respect.

When a user inputs a change (e.g., an addition, deletion, or modification) to a set of one or more facts already automatically extracted from a free-form narration, such a change is referred to herein as a “correction” to the set of extracted facts. In some embodiments, a user may input a correction to an extracted set of medical facts in any suitable way, and the fact review system may then apply the user's correction throughout the free-form narration. In such a way, in some embodiments, a user may be able to correct the fact extraction component's treatment of one portion of the narrative text, and similar corrections may then be applied automatically to other portions of the text, without the user having to directly specify the same type of correction for every similar portion of text in the document. For a non-limiting example, consider the exemplary narrative text below:

-   -   CHIEF COMPLAINT: Epileptic myoclonic twitches of the upper         extremity.     -   PAST MEDICAL HISTORY: History of developmental delay and         myoclonic seizure involving the upper extremities.     -   ASSESSMENT: Myoclonic jerks involving the upper extremities.

Assume that an automatic fact extraction component failed to extract the clinician's intended meaning (the intended medical fact) from the text portion “Epileptic myoclonic twitches of the upper extremity.” The text portions “myoclonic seizure involving the upper extremities” and “Myoclonic jerks involving the upper extremities” communicate similar semantic meanings, so the automatic fact extraction component is unlikely to successfully extract the intended medical fact from these text portions either. In some embodiments, a user could correct the fact extraction by selecting the text portion “Epileptic myoclonic twitches,” and adding a corresponding medical fact “myoclonic epileptic seizure,” which corresponds to ICD-9 code 345.1. In some embodiments, upon analyzing the user's correction to the fact extraction from the first portion of the text, the fact review system may learn from the association and may automatically apply similar corrections to the rest of the narrative text. For example, the fact review system may identify the other text portions “myoclonic seizure” and “myoclonic jerks” as being similar to the first text portion “Epileptic myoclonic seizures,” and may automatically extract the fact “myoclonic epileptic seizure,” corresponding to ICD-9 code 345.1, from the other two text portions as well. In this example, in some embodiments, the system may extract similar facts (e.g., facts that are not necessarily identical to the fact added by the user) from the other portions of the text, since the other text portions may have similar, but not necessarily identical, intended semantic meanings as the first text portion. For example, in the above narrative, both text portions “Epileptic myoclonic twitches” and “myoclonic seizure” indicate a medical problem with a normalized form of “myoclonic epileptic seizure,” but the second portion occurs in the “PAST MEDICAL HISTORY” section, while the first portion occurs in the “CHIEF COMPLAINT” section. Thus, in some embodiments, the system may automatically extract a similar medical fact from the second portion, but the fact extracted from the second portion may indicate that the problem is a past history problem rather than a current problem.

Thus, in some embodiments, a user may identify a fact that should be associated with a first portion of the narrative text, and the system may then automatically extract one or more similar facts from one or more other portions of the narrative text. The user may identify the fact that should be associated with the first text portion in any suitable way. For example, as discussed above, in some cases the user may select a portion of the narrative text, and may directly specify a fact that should be extracted from that portion of the text. In other cases, the fact extraction component may present to the user multiple options corresponding to alternative hypotheses for a fact to be extracted from the portion of the narrative text, and the user may identify the fact that should be associated with that text portion by selecting one of the alternative hypotheses presented. In still other cases, a user may select a fact that was already extracted from a portion of the narrative text, and may specify a modification that should be made to the extracted fact, thus identifying the correct fact that should be associated with the text portion. It should be appreciated, however, that the foregoing are merely examples, and a user may identify a fact that should be associated with a portion of the narrative text in any suitable way, as aspects of the invention are not limited in this respect.

In still other examples, a user may delete a fact that was extracted from a first portion of the narrative text, and the system may then automatically delete one or more other instances of the same extracted fact (or of similar extracted facts) from one or more other portions of the narrative text. It should further be appreciated, however, that adding, deleting, and modifying facts as described above are only examples, and the user may be permitted to correct a set of extracted medical facts in any suitable way, as aspects of the invention are not limited in this respect. In some embodiments, any suitable type of correction made by a user to one or more facts extracted from a first portion of a narrative text may then automatically be applied to one or more other portions of the narrative text. Furthermore, in some embodiments, any suitable type of correction made by a user to a set of facts extracted from a first narrative text may alternatively or additionally be automatically applied to other narrative texts processed by the fact extraction component in the future. In some embodiments, one or more fact extraction models used by the fact extraction component may be re-trained such that the correction applied to the first text may be reflected in the manner of processing later texts. Exemplary techniques for applying a user correction throughout the text in which it occurs, as well as exemplary techniques for reflecting such a correction in the processing of other texts, are described below.

In some instances, one or more such changes made to the set of facts corresponding to the current patient encounter may create one or more inconsistencies between the set of facts and the semantic content of the original free-form narration. For example, a clinician may originally specify a particular diagnosis in a free-form narration, and a fact extraction component may extract a clinical fact corresponding to that diagnosis. If the clinician later changes his mind and would like to replace the original diagnosis with a different diagnosis, he may have the option in some embodiments of simply editing the extracted fact directly, rather than editing the data representation of the free-form narration itself. Such a situation may create an inconsistency between the free-form narration and the corresponding set of clinical facts, as the facts may now specify the new diagnosis, and the free-form narration may still specify the original diagnosis. In such situations, the fact review system in some embodiments may alert the clinician or other user to the inconsistency, and/or may provide any of several options to the user to address the inconsistency. One option may be to ignore the inconsistency and allow it to persist in the clinical documentation. Another option may be to allow the user to edit the data representation of the free-form narration to be consistent with the current set of clinical facts. Another option may be to allow the system to automatically update the data representation of the free-form narration by adding, deleting or replacing one or more portions of the free-form narration. Yet another option may be simply to append a note to the free-form narration, indicating and optionally explaining the inconsistency.

In some embodiments, as discussed above, a medical fact review system may provide various tools for a clinician to review and/or edit facts corresponding to a current patient encounter, receive alerts generated based on those facts, review and/or edit a free-form narration of the patient encounter provided by the clinician, and/or review the linkages maintained between medical facts extracted by a fact extraction component and the portions of the free-form narration from which the medical facts were extracted. Such tools may be provided in any suitable form, including visual forms, audio forms, combined forms or any other form providing the functionality described herein, as aspects of the present invention are not limited in this respect. When the tools are provided in visual form, their functionality may be accessed through a graphical user interface (GUI). In some embodiments, the GUI may be organized in a way to allow the human user(s) to efficiently process the information displayed. For example, in some embodiments, text narratives, facts and alerts may be displayed in consistent locations within the user interface and organized by type and/or priority. Different colors, textual styles and/or graphical styles may be utilized to direct the user's attention to high-priority alerts, and/or to make linkages between related items in the display easily recognizable. In some embodiments, the organization and/or composition of such a visual display may be determined in accordance with principles used in the development of heads-up displays (HUDs).

In some embodiments, a fact review system operating on a set of clinical facts ascertained from a patient encounter may provide tools for promoting efficiency in the workflow of the clinician and/or other personnel beyond the conclusion of the patient encounter. For example, in some embodiments, the fact review system may interface with one or more Computerized Physician Order Entry (CPOE) systems to automatically place orders for prescriptions, laboratory tests, radiology screenings, surgical or other medical procedures and/or other planned treatment action items, based on such items (e.g., medication names, dosages, procedure names, dates, etc.) being specified in the set of facts corresponding to the current patient encounter. In some embodiments, such items may be identified based on their being extracted from a “plan” section of a free-form narration. In some embodiments, the fact review system may interface with one or more scheduling systems to schedule appointments for medical procedures and/or future office visits within or external to the institution. In some embodiments, the fact review system may format one or more facts into a standard or proprietary messaging format to facilitate interfacing with any of such systems. In some embodiments, billing reports, patient discharge instructions and/or other documents may be automatically generated or initially populated based on the set of clinical facts. In some embodiments with any of the above-described functionality, the fact review system may provide an alert to the user and/or may prompt for user or clinician approval prior to taking any of the above actions.

In some embodiments, a fact review system may provide tools for evidence-based clinical decision support based on the set of clinical facts collected for the current patient encounter. In some embodiments, the fact review system may have access to one or more data sets of past patient reports and/or one or more archives of medical literature documents that may provide information regarding various conditions, treatment outcomes and the like that are relevant to the current patient encounter. In some embodiments, the available documents may have been processed by the fact extraction component and indexed using the same system of terminology used to extract clinical facts from free-form clinical narrations. As such, in some embodiments, the facts corresponding to the current patient encounter may be efficiently matched to relevant available documents, and those documents or a subset thereof may be retrieved for display or otherwise provided to the clinician to aid in his determination of a treatment plan for the current patient. In some embodiments, a statistical model may be trained on the data set of past patient outcomes and/or on data in the medical literature, such that the system may go beyond mere presentation of references to actually predict best courses of treatment by applying the statistical model to the collection of facts corresponding to the current patient encounter and/or to the patient's medical history. In some embodiments, treatment recommendations may be provided to the clinician along with links to references in the literature or other available data supporting the recommendations. In some embodiments, clinical language understanding (CLU) indexing of large quantities of patient records and/or literature documents may also be used to facilitate clinical research studies, as available natural language documents may be efficiently mapped to an ad hoc query corresponding to a research question. From the resulting corpus of conceptually relevant documents, treatment outcomes and/or other required information or facts may be extracted using CLU technology to aid in synthesizing an answer to the research question.

While a number of inventive features for clinical documentation processes are described above, it should be appreciated that embodiments of the present invention may include any one of these features, any combination of two or more features, or all of the features, as aspects of the invention are not limited to any particular number or combination of the above-described features. The aspects of the present invention described herein can be implemented in any of numerous ways, and are not limited to any particular implementation techniques. Described below are examples of specific implementation techniques; however, it should be appreciate that these examples are provided merely for purposes of illustration, and that other implementations are possible.

One illustrative application for the techniques described herein is for use in a system for enhancing medical documentation processes. An exemplary operating environment for such a system is illustrated in FIG. 1. The exemplary operating environment includes a medical documentation system 100, which may be implemented in any suitable form, as aspects of the present invention are not limited in this respect. For example, system 100 may be implemented as a single stand-alone machine, or may be implemented by multiple distributed machines that share processing tasks in any suitable manner. System 100 may be implemented as one or more computers; an example of a suitable computer is described below. In some embodiments, system 100 may include one or more tangible, non-transitory computer-readable storage devices storing processor-executable instructions, and one or more processors that execute the processor-executable instructions to perform the functions described herein. The storage devices may be implemented as computer-readable storage media encoded with the processor-executable instructions; examples of suitable computer-readable storage media are discussed below.

As depicted, exemplary system 100 includes an ASR engine 102, a fact extraction component 104, and a fact review component 106. Each of these processing components of system 100 may be implemented in software, hardware, or a combination of software and hardware. Components implemented in software may comprise sets of processor-executable instructions that may be executed by the one or more processors of system 100 to perform the functionality described herein. Each of ASR engine 102, fact extraction component 104 and fact review component 106 may be implemented as a separate component of system 100, or any combination of these components may be integrated into a single component or a set of distributed components. In addition, any one of ASR engine 102, fact extraction component 104 and fact review component 106 may be implemented as a set of multiple software and/or hardware components. It should be understood that any such component depicted in FIG. 1 is not limited to any particular software and/or hardware implementation and/or configuration.

As illustrated in FIG. 1, user interface 110 is presented to a clinician 120, who may be a physician, a physician's aide, a nurse, or any other personnel involved in the evaluation and/or treatment of a patient 122 in a clinical setting. During the course of a clinical encounter with patient 122, or at some point thereafter, clinician 120 may wish to document the patient encounter. Such a patient encounter may include any interaction between clinician 120 and patient 122 in a clinical evaluation and/or treatment setting, including, but not limited to, an office visit, an interaction during hospital rounds, an outpatient or inpatient procedure (surgical or non-surgical), a follow-up evaluation, a visit for laboratory or radiology testing, etc. One method that clinician 120 may use to document the patient encounter may be to enter medical facts that can be ascertained from the patient encounter into user interface 110 as discrete structured data items. The set of medical facts, once entered, may be transmitted in some embodiments via any suitable communication medium or media (e.g., local and/or network connection(s) that may include wired and/or wireless connection(s)) to system 100. Specifically, in some embodiments, the set of medical facts may be received at system 100 by a fact review component 106, exemplary functions of which are described below.

Another method that may be used by clinician 120 to document the patient encounter is to provide a free-form narration of the patient encounter. In some embodiments, the narration may be free-form in the sense that clinician 120 may be unconstrained with regard to the structure and content of the narration, and may be free to provide any sequence of words, sentences, paragraphs, sections, etc., that he would like. In some embodiments, there may be no limitation on the length of the free-form narration, or the length may be limited only by the processing capabilities of the user interface into which it is entered or of the later processing components that will operate upon it. In other embodiments, the free-form narration may be constrained in length (e.g., limited to a particular number of characters).

A free-form narration of the patient encounter may be provided by clinician 120 in any of various ways. One way may be to manually enter the free-form narration in textual form into user interface 110, e.g., using a keyboard. In this respect, the one or more processors of system 100 and/or of a client device in communication with system 100 may in some embodiments be programmed to present a user interface including a text editor/word processor to clinician 120. Such a text editor/word processor may be implemented in any suitable way, as aspects of the present invention are not limited in this respect.

Another way to provide a free-form narration of the patient encounter may be to verbally speak a dictation of the patient encounter. Such a spoken dictation may be provided in any suitable way, as aspects of the present invention are not limited in this respect. As illustrated in FIG. 1, one way that clinician 120 may provide a spoken dictation of the free-form narration may be to speak the dictation into a microphone 112 providing input (e.g., via a direct wired connection, a direct wireless connection, or via a connection through an intermediate device) to user interface 110. An audio recording of the spoken dictation may then be stored in any suitable data format, and transmitted to system 100 and/or to medical transcriptionist 130. Another way that clinician 120 may provide the spoken dictation may be to speak into a telephone 118, from which an audio signal may be transmitted to be recorded at system 100, at the site of medical transcriptionist 130, or at any other suitable location. Alternatively, the audio signal may be recorded in any suitable data format at an intermediate facility, and the audio data may then be relayed to system 100 and/or to medical transcriptionist 130.

In some embodiments, medical transcriptionist 130 may receive the audio recording of the dictation provided by clinician 120, and may transcribe it into a textual representation of the free-form narration (e.g., into a text narrative). Medical transcriptionist 130 may be any human who listens to the audio dictation and writes or types what was spoken into a text document. In some embodiments, medical transcriptionist 130 may be specifically trained in the field of medical transcription, and may be well-versed in medical terminology. In some embodiments, medical transcriptionist 130 may transcribe exactly what she hears in the audio dictation, while in other embodiments, medical transcriptionist 130 may add formatting to the text transcription to comply with generally accepted medical document standards. When medical transcriptionist 130 has completed the transcription of the free-form narration into a textual representation, the resulting text narrative may in some embodiments be transmitted to system 100 or any other suitable location (e.g., to a storage location accessible to system 100). Specifically, in some embodiments the text narrative may be received from medical transcriptionist 130 by fact extraction component 104 within system 100. Exemplary functionality of fact extraction component 104 is described below.

In some other embodiments, the audio recording of the spoken dictation may be received, at system 100 or any other suitable location, by automatic speech recognition (ASR) engine 102. In some embodiments, ASR engine 102 may then process the audio recording to determine what was spoken. As discussed above, such processing may involve any suitable speech recognition technique, as aspects of the present invention are not limited in this respect. In some embodiments, the audio recording may be automatically converted to a textual representation, while in other embodiments, words identified directly from the audio recording may be represented in a data format other than text, or abstract concepts may be identified instead of words. Examples of further processing are described below with reference to a text narrative that is a textual representation of the free-form narration; however, it should be appreciated that similar processing may be performed on other representations of the free-form narration as discussed above. When a textual representation is produced, in some embodiments it may be reviewed by a human (e.g., a transcriptionist) for accuracy, while in other embodiments the output of ASR engine 102 may be accepted as accurate without human review. As discussed above, some embodiments are not limited to any particular method for transcribing audio data; an audio recording of a spoken dictation may be transcribed manually by a human transcriptionist, automatically by ASR, or semiautomatically by human editing of a draft transcription produced by ASR. Transcriptions produced by ASR engine 102 and/or by transcriptionist 130 may be encoded or otherwise represented as data in any suitable form, as aspects of the invention are not limited in this respect.

In some embodiments, ASR engine 102 may make use of a lexicon of medical terms (which may be part of, or in addition to, another more general speech recognition lexicon) while determining the sequence of words that were spoken in the free-form narration provided by clinician 120. However, aspects of the invention are not limited to the use of a lexicon, or any particular type of lexicon, for ASR. When used, the medical lexicon in some embodiments may be linked to a knowledge representation model such as a clinical language understanding ontology utilized by fact extraction component 104, such that ASR engine 102 might produce a text narrative containing terms in a form understandable to fact extraction component 104. In some embodiments, a more general speech recognition lexicon might also be shared between ASR engine 102 and fact extraction component 104. However, in other embodiments, ASR engine 102 may not have any lexicon developed to be in common with fact extraction component 104. In some embodiments, a lexicon used by ASR engine 102 may be linked to a different type of medical knowledge representation model, such as one not designed or used for language understanding. It should be appreciated that any lexicon used by ASR engine 102 and/or fact extraction component 104 may be implemented and/or represented as data in any suitable way, as aspects of the invention are not limited in this respect.

In some embodiments, a text narrative, whether produced by ASR engine 102 (and optionally verified or not by a human), produced by medical transcriptionist 130, directly entered in textual form through user interface 110, or produced in any other way, may be re-formatted in one or more ways before being received by fact extraction component 104. Such re-formatting may be performed by ASR engine 102, by a component of fact extraction component 104, by a combination of ASR engine 102 and fact extraction component 104, or by any other suitable software and/or hardware component. In some embodiments, the re-formatting may be performed in a way known to facilitate fact extraction, and may be performed for the purpose of facilitating the extraction of clinical facts from the text narrative by fact extraction component 104. For example, in some embodiments, processing to perform fact extraction may be improved if sentence boundaries in the text narrative are accurate. Accordingly, in some embodiments, the text narrative may be re-formatted prior to fact extraction to add, remove or correct one or more sentence boundaries within the text narrative. In some embodiments, this may involve altering the punctuation in at least one location within the text narrative. In another example, fact extraction may be improved if the text narrative is organized into sections with headings, and thus the re-formatting may include determining one or more section boundaries in the text narrative and adding, removing or correcting one or more corresponding section headings. In some embodiments, the re-formatting may include normalizing one or more section headings (which may have been present in the original text narrative and/or added or corrected as part of the re-formatting) according to a standard for the healthcare institution corresponding to the patient encounter (which may be an institution-specific standard or a more general standard for section headings in clinical documents). In some embodiments, a user (such as clinician 120, medical transcriptionist 130, or another user) may be prompted to approve the re-formatted text.

Any suitable technique(s) for implementing re-formatting, examples of which are described above, may be employed, as aspects of the invention are not limited in this respect. One exemplary technique suitable for performing re-formatting of a text narrative is described in U.S. patent application Ser. No. 11/322,971, filed on Dec. 30, 2005, entitled “Translating Literal Speech to Formatted Text”, which is incorporated herein by reference in its entirety. Another exemplary technique that may be used in some embodiments for performing re-formatting of a text narrative involves the use of word N-gram statistical models to predict sentence and/or section boundaries in a text narrative. Such statistical models may be trained on a corpus of documents (e.g., past medical records) with correct punctuation and/or section headings (e.g., supplied by a medical transcriptionist).

In some embodiments, a statistical model may add punctuation (e.g., periods, exclamation points, question marks, etc.) to add one or more sentence boundaries to a text narrative by computing a probability, for each word in the text narrative, that a particular punctuation mark should follow that word. In computing the probability that a word should be followed by a punctuation mark, the statistical model may consider the N-word sequence from the text narrative that ends with that word, and determine the frequency with which that N-word sequence is followed by that punctuation mark in the training data for the statistical model. A lattice may then be constructed using the computed probabilities for all the words in the text narrative, or in a portion of the text narrative, and the best path in terms of combined probability through the lattice may be determined. Where punctuation marks are located in the best path through the lattice, those punctuation marks may be added in those locations to the text narrative in producing the formatted text. In some embodiments, another statistical model may add section headings, corresponding to section boundaries, in a similar fashion. For example, in some embodiments, a statistical model for section headings may compute probabilities, for each word, that the word should be followed by a section boundary. In some embodiments, in computing probabilities, a statistical model for section headings may consider more words that follow the current word than words that precede the current word. In some embodiments, one or more separate statistical models may be trained to delete incorrect sentence and/or section boundaries. Those models in some embodiments may be trained through feedback from clinician 120 or another user, by observing word sequences (initially including punctuation and/or section boundaries) from which clinician 120 or another user tends to remove the punctuation and/or section boundaries when editing.

In some embodiments, either an original or a re-formatted text narrative may be received by fact extraction component 104, which may perform processing to extract one or more medical facts (e.g., clinical facts) from the text narrative. The text narrative may be received from ASR engine 102, from medical transcriptionist 130, directly from clinician 120 via user interface 110, or in any other suitable way. Any suitable technique(s) for extracting facts from the text narrative may be used, as aspects of the present invention are not limited in this respect. Exemplary techniques for medical fact extraction are described below.

In some embodiments, a fact extraction component may be implemented using techniques such as those described in U.S. Pat. No. 7,493,253, entitled “Conceptual World Representation Natural Language Understanding System and Method.” U.S. Pat. No. 7,493,253 is incorporated herein by reference in its entirety. Such a fact extraction component may make use of a formal ontology linked to a lexicon of clinical terms. The formal ontology may be implemented as a relational database, or in any other suitable form, and may represent semantic concepts relevant to the medical domain, as well as linguistic concepts related to ways the semantic concepts may be expressed in natural language.

In some embodiments, concepts in a formal ontology used by a fact extraction component may be linked to a lexicon of medical terms and/or codes, such that each medical term and each code is linked to at least one concept in the formal ontology. In some embodiments, the lexicon may include the standard medical terms and/or codes used by the institution in which the fact extraction component is applied. For example, the standard medical terms and/or codes used by an EHR maintained by the institution may be included in the lexicon linked to the fact extraction component's formal ontology. In some embodiments, the lexicon may also include additional medical terms used by the various clinicians within the institution, and/or used by clinicians generally, when describing medical issues in a free-form narration. Such additional medical terms may be linked, along with their corresponding standard medical terms, to the appropriate shared concepts within the formal ontology. For example, the standard term “acute myocardial infarction” as well as other corresponding terms such as “heart attack”, “acute MI” and “AMI” may all be linked to the same abstract concept in the formal ontology—a concept representing an interruption of blood supply to the heart. Such linkage of multiple medical terms to the same abstract concept in some embodiments may relieve the clinician of the burden of ensuring that only standard medical terms preferred by the institution appear in the free-form narration. For example, in some embodiments, a clinician may be free to use the abbreviation “AMI” or the colloquial “heart attack” in his free-form narration, and the shared concept linkage may allow the fact extraction component to nevertheless automatically extract a fact corresponding to “acute myocardial infarction”.

In some embodiments, a formal ontology used by a fact extraction component may also represent various types of relationships between the concepts represented. One type of relationship between two concepts may be a parent-child relationship, in which the child concept is a more specific version of the parent concept. More formally, in a parent-child relationship, the child concept inherits all necessary properties of the parent concept, while the child concept may have necessary properties that are not shared by the parent concept. For example, “heart failure” may be a parent concept, and “congestive heart failure” may be a child concept of “heart failure.” In some embodiments, any other type(s) of relationship useful to the process of medical documentation may also be represented in the formal ontology. For example, one type of relationship may be a symptom relationship. In one example of a symptom relationship, a concept linked to the term “chest pain” may have a relationship of “is-symptom-of” to the concept linked to the term “heart attack”. Other types of relationships may include complication relationships, comorbidity relationships, interaction relationships (e.g., among medications), and many others. Any number and type(s) of concept relationships may be included in such a formal ontology, as aspects of the present invention are not limited in this respect.

In some embodiments, automatic extraction of medical facts from a clinician's free-form narration may involve parsing the free-form narration to identify medical terms that are represented in the lexicon of the fact extraction component. Concepts in the formal ontology linked to the medical terms that appear in the free-form narration may then be identified, and concept relationships in the formal ontology may be traced to identify further relevant concepts. Through these relationships, as well as the linguistic knowledge represented in the formal ontology, one or more medical facts may be extracted. For example, if the free-form narration includes the medical term “hypertension” and the linguistic context relates to the patient's past, the fact extraction component may automatically extract a fact indicating that the patient has a history of hypertension. On the other hand, if the free-form narration includes the medical term “hypertension” in a sentence about the patient's mother, the fact extraction component may automatically extract a fact indicating that the patient has a family history of hypertension. In some embodiments, relationships between concepts in the formal ontology may also allow the fact extraction component to automatically extract facts containing medical terms that were not explicitly included in the free-form narration. For example, the medical term “meningitis” can also be described as inflammation in the brain. If the free-form narration includes the terms “inflammation” and “brain” in proximity to each other, then relationships in the formal ontology between concepts linked to the terms “inflammation”, “brain” and “meningitis” may allow the fact extraction component to automatically extract a fact corresponding to “meningitis”, despite the fact that the term “meningitis” was not stated in the free-form narration.

It should be appreciated that the foregoing descriptions are provided by way of example only, and that any suitable technique(s) for extracting a set of one or more medical facts from a free-form narration may be used, as aspects of the present invention are not limited to any particular fact extraction technique. For instance, it should be appreciated that fact extraction component 104 is not limited to the use of an ontology, as other forms of knowledge representation models, including statistical models and/or rule-based models, may also be used. The knowledge representation model may also be represented as data in any suitable format, and may be stored in any suitable location, such as in a storage medium of system 100 accessible by fact extraction component 104, as aspects of the invention are not limited in this respect. In addition, a knowledge representation model such as an ontology used by fact extraction component 104 may be constructed in any suitable way, as aspects of the invention are not limited in this respect.

For instance, in some embodiments a knowledge representation model may be constructed manually by one or more human developers with access to expert knowledge about medical facts, diagnoses, problems, potential complications, comorbidities, appropriate observations and/or clinical findings, and/or any other relevant information. In other embodiments, a knowledge representation model may be generated automatically, for example through statistical analysis of past medical reports documenting patient encounters, of medical literature and/or of other medical documents. Thus, in some embodiments, fact extraction component 104 may have access to a data set 170 of medical literature and/or other documents such as past patient encounter reports. In some embodiments, past reports and/or other text documents may be marked up (e.g., by a human) with labels indicating the nature of the relevance of particular statements in the text to the patient encounter or medical topic to which the text relates. A statistical knowledge representation model may then be trained to form associations based on the prevalence of particular labels corresponding to similar text within an aggregate set of multiple marked up documents. For example, if “pneumothorax” is labeled as a “complication” in a large enough proportion of clinical procedure reports documenting pacemaker implantation procedures, a statistical knowledge representation model may generate and store a concept relationship that “pneumothorax is-complication-of pacemaker implantation.” In some embodiments, automatically generated and hard coded (e.g., by a human developer) concepts and/or relationships may both be included in a knowledge representation model used by fact extraction component 104.

As discussed above, it should be appreciated that aspects of the invention are not limited to any particular technique(s) for constructing knowledge representation models. Examples of suitable techniques include those disclosed in the following:

-   Gómez-Pérez, A., and Manzano-Macho, D. (2005). An overview of     methods and tools for ontology learning from texts. Knowledge     Engineering Review 19, p. 187-212. -   Cimiano, P., and Staab, S. (2005). Learning concept hierarchies from     text with a guided hierarchical clustering algorithm. In C. Biemann     and G. Paas (eds.), Proceedings of the ICML 2005 Workshop on     Learning and Extending Lexical Ontologies with Machine Learning     Methods, Bonn, Germany. -   Fan, J., Ferrucci, D., Gondek, D., and Kalyanpur, A. (2010).     PRISMATIC: Inducing Knowledge from a Lange Scale Lexicalized     Relation Resource. NAACL Workshop on Formalisms and Methodology for     Learning by Reading. -   Welty, C., Fan, J., Gondek, D. and Schlaikjer, A. (2010). Large     scale relation detection. NAACL Workshop on Formalisms and     Methodology for Learning by Reading.

Each of the foregoing publications is incorporated herein by reference in its entirety.

Alternatively or additionally, in some embodiments a fact extraction component may make use of one or more statistical models to extract semantic entities from natural language input. In general, a statistical model can be described as a functional component designed and/or trained to analyze new inputs based on probabilistic patterns observed in prior training inputs. In this sense, statistical models differ from “rule-based” models, which typically apply hard-coded deterministic rules to map from inputs having particular characteristics to particular outputs. By contrast, a statistical model may operate to determine a particular output for an input with particular characteristics by considering how often (e.g., with what probability) training inputs with those same characteristics (or similar characteristics) were associated with that particular output in the statistical model's training data. To supply the probabilistic data that allows a statistical model to extrapolate from the tendency of particular input characteristics to be associated with particular outputs in past examples, statistical models are typically trained (or “built”) on large training corpuses with great numbers of example inputs. Typically the example inputs are labeled with the known outputs with which they should be associated, usually by a human labeler with expert knowledge of the domain. Characteristics of interest (known as “features”) are identified (“extracted”) from the inputs, and the statistical model learns the probabilities with which different features are associated with different outputs, based on how often training inputs with those features are associated with those outputs. When the same features are extracted from a new input (e.g., an input that has not been labeled with a known output by a human), the statistical model can then use the learned probabilities for the extracted features (as learned from the training data) to determine which output is most likely correct for the new input. Exemplary implementations of a fact extraction component using one or more statistical models are described further below.

In some embodiments, fact extraction component 104 may utilize a statistical fact extraction model based on entity detection and/or tracking techniques, such as those disclosed in: Florian, R., Hassan, H., Ittycheriah, A., Jing, H., Kambhatla, N., Luo, X., Nicolov, N., and Roukos, S. (2004). A Statistical Model for Multilingual Entity Detection and Tracking. Proceedings of the Human Language Technologies Conference 2004 (HLT-NAACL'04). This publication is incorporated herein by reference in its entirety.

For example, in some embodiments, a list of fact types of interest for generating medical reports may be defined, e.g., by a developer of fact extraction component 104. Such fact types (also referred to herein as “entity types”) may include, for example, problems, disorders (a disorder is a type of problem), diagnoses (a diagnosis may be a disorder that a clinician has identified as a problem for a particular patient), findings (a finding is a type of problem that need not be a disorder), medications, body sites, social history facts, allergies, diagnostic test results, vital signs, procedures, procedure steps, observations, devices, and/or any other suitable medical fact types. It should be appreciated that any suitable list of fact types may be utilized, and may or may not include any of the fact types listed above, as aspects of the invention are not limited in this respect. In some embodiments, spans of text in a set of sample patient encounter reports may be labeled (e.g., by a human) with appropriate fact types from the list. A statistical model may then be trained on the corpus of labeled sample reports to detect and/or track such fact types as semantic entities, using entity detection and/or tracking techniques, examples of which are described below.

For example, in some embodiments, a large number of past free-form narrations created by clinicians may be manually labeled to form a corpus of training data for a statistical entity detection model. As discussed above, in some embodiments, a list of suitable entities may be defined (e.g., by a domain administrator) to include medical fact types that are to be extracted from future clinician narrations. One or more human labelers (e.g., who may have specific knowledge about medical information and typical clinician narration content) may then manually label portions of the training texts with the particular defined entities to which they correspond. For example, given the training text, “Patient is complaining of acute sinusitis,” a human labeler may label the text portion “acute sinusitis” with the entity label “Problem.” In another example, given the training text, “He has sinusitis, which appears to be chronic,” a human labeler may label the text “sinusitis” and “chronic” with a single label indicating that both words together correspond to a “Problem” entity. As should be clear from these examples, the portion of the text labeled as corresponding to a single conceptual entity need not be formed of contiguous words, but may have words split up within the text, having non-entity words in between.

In some embodiments, the labeled corpus of training data may then be processed to build a statistical model trained to detect mentions of the entities labeled in the training data. Each time the same conceptual entity appears in a text, that appearance is referred to as a mention of that entity. For example, consider the text, “Patient has sinusitis. His sinusitis appears to be chronic.” In this example, the entity detection model may be trained to identify each appearance of the word “sinusitis” in the text as a separate mention of the same “Problem” entity.

In some embodiments, the process of training a statistical entity detection model on labeled training data may involve a number of steps to analyze each training text and probabilistically associate its characteristics with the corresponding entity labels. In some embodiments, each training text (e.g., free-form clinician narration) may be tokenized to break it down into various levels of syntactic substructure. For example, in some embodiments, a tokenizer module may be implemented to designate spans of the text as representing structural/syntactic units such as document sections, paragraphs, sentences, clauses, phrases, individual tokens, words, sub-word units such as affixes, etc. In some embodiments, individual tokens may often be single words, but some tokens may include a sequence of more than one word that is defined, e.g., in a dictionary, as a token. For example, the term “myocardial infarction” could be defined as a token, although it is a sequence of more than one word. In some embodiments, a token's identity (i.e., the word or sequence of words itself) may be used as a feature of that token. In some embodiments, the token's placement within particular syntactic units in the text (e.g., its section, paragraph, sentence, etc.) may also be used as features of the token.

In some embodiments, an individual token within the training text may be analyzed (e.g., in the context of the surrounding sentence) to determine its part of speech (e.g., noun, verb, adjective, adverb, preposition, etc.), and the token's part of speech may be used as a further feature of that token. In some embodiments, each token may be tagged with its part of speech, while in other embodiments, not every token may be tagged with a part of speech. In some embodiments, a list of relevant parts of speech may be pre-defined, e.g., by a developer of the statistical model, and any token having a part of speech listed as relevant may be tagged with that part of speech. In some embodiments, a parser module may be implemented to determine the syntactic structure of sentences in the text, and to designate positions within the sentence structure as features of individual tokens. For example, in some embodiments, the fact that a token is part of a noun phrase or a verb phrase may be used as a feature of that token. Any type of parser may be used, non-limiting examples of which include a bottom-up parser and/or a dependency parser, as aspects of the invention are not limited in this respect.

In some embodiments, section membership may be used as a feature of a token. In some embodiments, a section normalization module may be implemented to associate various portions of the narrative text with the proper section to which it should belong. In some embodiments, a set of standardized section types (e.g., identified by their section headings) may be defined for all texts, or a different set of normalized section headings may be defined for each of a number of different types of texts (e.g., corresponding to different types of documents). For example, in some embodiments, a different set of normalized section headings may be defined for each type of medical document in a defined set of medical document types. Non-limiting examples of medical document types include consultation reports, history & physical reports, discharge summaries, and emergency room reports, although there are also many other examples. In the medical field, the various types of medical documents are often referred to as “work types.” In some cases, the standard set of sections for various types of medical documents may be established by a suitable system standard, institutional standard, or more widely applicable standard, such as the Meaningful Use standard (discussed above) or the Logical Observation Identifiers Names and Codes (LOINC) standard maintained by the Regenstrief Institute. For example, an expected set of section headings for a history & physical report under the Meaningful Use standard may include headings for a “Reason for Visit” section, a “History of Present Illness” section, a “History of Medication Use” section, an “Allergies, Adverse Reactions and Alerts” section, a “Review of Systems” section, a “Social History” section, a “Physical Findings” section, an “Assessment and Plan” section, and/or any other suitable section(s). Any suitable set of sections may be used, however, as aspects of the invention are not limited in this respect.

A section normalization module may use any suitable technique to associate portions of text with normalized document sections, as aspects of the invention are not limited in this respect. In some embodiments, the section normalization module may use a table (e.g., stored as data in a storage medium) to map text phrases that commonly occur in medical documents to the sections to which they should belong. In another example, a statistical model may be trained to determine the most likely section for a portion of text based on its semantic content, the semantic content of surrounding text portions, and/or the expected semantic content of the set of normalized sections. In some embodiments, once a normalized section for a portion of text has been identified, the membership in that section may be used as a feature of one or more tokens in that portion of text.

In some embodiments, other types of features may be extracted, i.e., identified and associated with tokens in the training text. For example, in some embodiments, an N-gram feature may identify the previous (N−1) words and/or tokens in the text as a feature of the current token. In another example, affixes (e.g., suffixes such as -ectomy, -oma, -itis, etc.) may be used as features of tokens. In another example, one or more predefined dictionaries and/or ontologies may be accessed, and a token's membership in any of those dictionaries may be used as a feature of that token. For example, a predefined dictionary of surgical procedures may be accessed, and/or a dictionary of body sites, and/or a dictionary of known diseases, etc. It should be appreciated, however, that all of the foregoing feature types are merely examples, and any suitable number and/or types of features of interest may be designated, e.g., by a developer of the statistical entity detection model, as aspects of the invention are not limited in this respect.

In some embodiments, the corpus of training text with its hand-labeled fact type entity labels, along with the collection of features extracted for tokens in the text, may be input to the statistical entity detection model for training. As discussed above, examples of suitable features include position within document structure, syntactic structure, parts of speech, parser features, N-gram features, affixes (e.g., prefixes and/or suffixes), membership in dictionaries (sometimes referred to as “gazetteers”) and/or ontologies, surrounding token contexts (e.g., a certain number of tokens to the left and/or right of the current token), orthographic features (e.g., capitalization, letters vs. numbers, etc.), entity labels assigned to previous tokens in the text, etc. As one non-limiting example, consider the training sentence, “Patient is complaining of acute sinusitis,” for which the word sequence “acute sinusitis” was hand-labeled as being a “Problem” entity. In one exemplary implementation, features extracted for the token “sinusitis” may include the token identity feature that the word is “sinusitis,” a syntactic feature specifying that the token occurred at the end of a sentence (e.g., followed by a period), a part-of-speech feature of “noun,” a parser feature that the token is part of a noun phrase (“acute sinusitis”), a trigram feature that the two preceding words are “of acute,” an affix feature of “-itis,” and a dictionary feature that the token is a member of a predefined dictionary of types of inflammation. It should be appreciated, however, that the foregoing list of features is merely exemplary, as any suitable features may be used. Aspects of the invention are not limited to any of the features listed above, and implementations including some, all, or none of the above features, as well as implementations including features not listed above, are possible.

In some embodiments, given the extracted features and manual entity labels for the entire training corpus as input, the statistical entity detection model may be trained to be able to probabilistically label new texts (e.g., texts not included in the training corpus) with automatic entity labels using the same feature extraction technique that was applied to the training corpus. In other words, by processing the input features and manual entity labels of the training corpus, the statistical model may learn probabilistic relationships between the features and the entity labels. When later presented with an input text without manual entity labels, the statistical model may then apply the same feature extraction techniques to extract features from the input text, and may apply the learned probabilistic relationships to automatically determine the most likely entity labels for word sequences in the input text. Any suitable statistical modeling technique may be used to learn such probabilistic relationships, as aspects of the invention are not limited in this respect. Non-limiting examples of suitable known statistical modeling techniques include machine learning techniques such as maximum entropy modeling, support vector machines, and conditional random fields, among others.

In some embodiments, training the statistical entity detection model may involve learning, for each extracted feature, a probability with which tokens having that feature are associated with each entity type. For example, for the suffix feature “-itis,” the trained statistical entity detection model may store a probability p1 that a token with that feature should be labeled as being part of a “Problem” entity, a probability p2 that a token with that feature should be labeled as being part of a “Medication” entity, etc. In some embodiments, such probabilities may be learned by determining the frequency with which tokens having the “-itis” feature were hand-labeled with each different entity label in the training corpus. In some embodiments, the probabilities may be normalized such that, for each feature, the probabilities of being associated with each possible entity (fact type) may sum to 1. However, aspects of the invention are not limited to such normalization. In some embodiments, each feature may also have a probability p0 of not being associated with any fact type, such that the non-entity probability p0 plus the probabilities of being associated with each possible fact type sum to 1 for a given feature. In other embodiments, separate classifiers may be trained for each fact type, and the classifiers may be run in parallel. For example, the “-itis” feature may have probability p1 of being part of a “Problem” entity and probability (1−p1) of not being part of a “Problem” entity, probability p2 of being part of a “Medication” entity and probability (1−p2) of not being part of a “Medication” entity, and so on. In some embodiments, training separate classifiers may allow some word sequences to have a non-zero probability of being labeled with more than one fact type simultaneously; for example, “kidney failure” could be labeled as representing both a Body Site and a Problem. In some embodiments, classifiers may be trained to identify sub-portions of an entity label. For example, the feature “-itis” could have a probability p_(B) of its token being at the beginning of a “Problem” entity label, a probability p_(I) of its token being inside a “Problem” entity label (but not at the beginning of the label), and a probability p_(O) of its token being outside a “Problem” entity label (i.e., of its token not being part of a “Problem” entity).

In some embodiments, the statistical entity detection model may be further trained to weight the individual features of a token to determine an overall probability that it should be associated with a particular entity label. For example, if the token “sinusitis” has n extracted features f1 . . . fn having respective probabilities p1 . . . pn of being associated with a “Problem” entity label, the statistical model may be trained to apply respective weights w1 . . . wn to the feature probabilities, and then combine the weighted feature probabilities in any suitable way to determine the overall probability that “sinusitis” should be part of a “Problem” entity. Any suitable technique for determining such weights may be used, including known modeling techniques such as maximum entropy modeling, support vector machines, conditional random fields, and/or others, as aspects of the invention are not limited in this respect.

In some embodiments, when an unlabeled text is input to the trained statistical entity detection model, the model may process the text to extract features and determine probabilities for individual tokens of being associated with various entity (e.g., fact type) labels. In some embodiments, the most probable label (including the non-entity label, if it is most probable) may be selected for each token in the input text. In other embodiments, labels may be selected through more contextual analysis, such as at the phrase level or sentence level, rather than at the token level. Any suitable technique, such as Viterbi techniques, or any other suitable technique, may be used, as aspects of the invention are not limited in this respect. In some embodiments, a lattice may be constructed of the associated probabilities for all entity types for all tokens in a sentence, and the best (e.g., highest combined probability) path through the lattice may be selected to determine which word sequences in the sentence are to be automatically labeled with which entity (e.g., fact type) labels. In some embodiments, not only the best path may be identified, but also the (N−1)-best alternative paths with the next highest associated probabilities. In some embodiments, this may result in an N-best list of alternative hypotheses for fact type labels to be associated with the same input text.

In some embodiments, a statistical model may also be trained to associate fact types extracted from new reports with particular facts to be extracted from those reports (e.g., to determine a particular concept represented by the text portion that has been labeled as an entity mention). For example, in some embodiments, a statistical fact extraction model may be applied to automatically label “acute sinusitis” not only with the “Problem” entity (fact type) label, but also with a label indicating the particular medical fact (e.g., concept) indicated by the word sequence (e.g., the medical fact “sinusitis, acute”). In such embodiments, for example, a single statistical model may be trained to detect specific particular facts as individual entities. For example, in some embodiments, the corpus of training text may be manually labeled by one or more human annotators with labels indicating specific medical facts, rather than labels indicating more general entities such as fact types or categories. However, in other embodiments, the process of detecting fact types as entities may be separated from the process of relating detected fact types to particular facts. For example, in some embodiments, a separate statistical model (e.g., an entity detection model) may be trained to automatically label portions of text with fact type labels, and another separate statistical model (e.g., a relation model) may be trained to identify which labeled entity (fact type) mentions together indicate a single specific medical fact. In some cases, the relation model may identify particular medical facts by relating together two or more mentions labeled with the same entity type.

For example, in the text, “Patient is complaining of acute sinusitis,” in some embodiments an entity detection model may label the tokens “acute” and “sinusitis” as being part of a “Problem” entity. In some embodiments, a relation model, given that “acute” and “sinusitis” have been labeled as “Problem,” may then relate the two tokens together to a single medical fact of “sinusitis, acute.” For another example, consider the text, “Patient has sinusitis, which appears to be chronic.” In some embodiments, an entity detection model may be applied to label the tokens “sinusitis” and “chronic” as “Problem” entity mentions. In some embodiments, a relation model may then be applied to determine that the two “Problem” entity mentions “sinusitis” and “chronic” are related (even though they are not contiguous in the text) to represent a single medical fact of “sinusitis, chronic.” For yet another example, consider the text, “She has acute sinusitis; chronic attacks of asthma may be a factor.” In some embodiments, an entity detection model may label each of the tokens “acute,” “sinusitis,” “chronic,” and “asthma” as belonging to “Problem” entity mentions. In some embodiments, a relation model may then be applied to determine which mentions relate to the same medical fact. For example, the relation model may determine that the tokens “acute” and “sinusitis” relate to a first medical fact (e.g., “sinusitis, acute”), while the tokens “chronic” and “asthma” relate to a different medical fact (e.g., “asthma, chronic”), even though the token “chronic” is closer in the sentence to the token “sinusitis” than to the token “asthma.”

In some embodiments, a relation model may be trained statistically using methods similar to those described above for training the statistical entity detection model. For example, in some embodiments, training texts may be manually labeled with various types of relations between entity mentions and/or tokens within entity mentions. For example, in the training text, “Patient has sinusitis, which appears to be chronic,” a human annotator may label the “Problem” mention “chronic” as having a relation to the “Problem” mention “sinusitis,” since both mentions refer to the same medical fact. In some embodiments, the relation annotations may simply indicate that certain mentions are related to each other, without specifying any particular type of relationship. In other embodiments, relation annotations may also indicate specific types of relations between entity mentions. Any suitable number and/or types of relation annotations may be used, as aspects of the invention are not limited in this respect. For example, in some embodiments, one type of relation annotation may be a “split” relation label. The tokens “sinusitis” and “chronic,” for example, may be labeled as having a split relationship, because “sinusitis” and “chronic” together make up an entity, even though they are not contiguous within the text. In this case, “sinusitis” and “chronic” together indicate a specific type of sinusitis fact, i.e., one that it is chronic and not, e.g., acute. Another exemplary type of relation may be an “attribute” relation. In some embodiments, one or more system developers may define sets of attributes for particular fact types, corresponding to related information that may be specified for a fact type. For example, a “Medication” fact type may have attributes “dosage,” “route,” “frequency,” “duration,” etc. In another example, an “Allergy” fact type may have attributes “allergen,” “reaction,” “severity,” etc. It should be appreciated, however, that the foregoing are merely examples, and that aspects of the invention are not limited to any particular attributes for any particular fact types. Also, other types of fact relations are possible, including family relative relations, causes-problem relations, improves-problem relations, and many others. Aspects of the invention are not limited to use of any particular relation types.

In some embodiments, using techniques similar to those described above, the labeled training text may be used as input to train the statistical relation model by extracting features from the text, and probabilistically associating the extracted features with the manually supplied labels. Any suitable set of features may be used, as aspects of the invention are not limited in this respect. For example, in some embodiments, features used by a statistical relation model may include entity (e.g., fact type) labels, parts of speech, parser features, N-gram features, token window size (e.g., a count of the number of words or tokens present between two tokens that are being related to each other), and/or any other suitable features. It should be appreciated, however, that the foregoing features are merely exemplary, as embodiments are not limited to any particular list of features. In some embodiments, rather than outputting only the best (e.g., most probable) hypothesis for relations between entity mentions, a statistical relation model may output a list of multiple alternative hypotheses, e.g., with corresponding probabilities, of how the entity mentions labeled in the input text are related to each other. In yet other embodiments, a relation model may be hard-coded and/or otherwise rule-based, while the entity detection model used to label text portions with fact types may be trained statistically.

In some embodiments, the relation model or another statistical model may also be trained to track mentions of the same entity from different sentences and/or document sections and to relate them together. Exemplary techniques for entity tracking are described in the publication by Florian cited above.

In some embodiments, further processing may be applied to normalize particular facts extracted from the text to standard forms and/or codes in which they are to be documented. For example, medical personnel often have many different ways of phrasing the same medical fact, and a normalization/coding process in some embodiments may be applied to identify the standard form and/or code corresponding to each extracted medical fact that was stated in a non-standard way. The standard form and/or code may be derived from any suitable source, as aspects of the invention are not limited in this respect. Some standard terms and/or codes may be derived from a government or profession-wide standard, such as SNOMED (Systematized Nomenclature of Medicine), UMLS (Unified Medical Language System), RxNorm, RadLex, etc. Other standard terms and/or codes may be more locally derived, such as from standard practices of a particular locality or institution. Still other standard terms and/or codes may be specific to the documentation system including the fact extraction component being applied.

For example, given the input text, “His sinuses are constantly inflamed,” in some embodiments, an entity detection model together with a relation model (or a single model performing both functions) may identify the tokens “sinuses,” “constantly” and “inflamed” as representing a medical fact. In some embodiments, a normalization/coding process may then be applied to identify the standard form for documenting “constantly inflamed sinuses” as “sinusitis, chronic.” Alternatively or additionally, in some embodiments the normalization/coding process may identify a standard code used to document the identified fact. For example, the ICD-9 code for “sinusitis, chronic” is ICD-9 code #473. Any suitable coding system may be used, as aspects of the invention are not limited in this respect. Exemplary standard codes include ICD (International Classification of Diseases) codes, CPT (Current Procedural Terminology) codes, E&M (Evaluation and Management) codes, MedDRA (Medical Dictionary for Regulatory Activities) codes, SNOMED codes, LOINC (Logical Observation Identifiers Names and Codes) codes, RxNorm codes, NDC (National Drug Code) codes and RadLex codes.

In some embodiments, a normalization/coding process may be rule-based (e.g., using lists of possible ways of phrasing particular medical facts, and/or using an ontology of medical terms and/or other language units to normalize facts extracted from input text to their standard forms). For example, in some embodiments, the tokens identified in the text as corresponding to a medical fact may be matched to corresponding terms in an ontology. In some embodiments, a list of closest matching terms may be generated, and may be ranked by their similarity to the tokens in the text. The similarity may be scored in any suitable way. For example, in one suitable technique, one or more tokens in the text may be considered as a vector of its component elements, such as words, and each of the terms in the ontology may also be considered as a vector of component elements such as words. Similarity scores between the tokens may then be computed by comparing the corresponding vectors, e.g., by calculating the angle between the vectors, or a related measurement such as the cosine of the angle. In some embodiments, one or more concepts that are linked in the ontology to one or more of the higher ranking terms (e.g., the terms most similar to the identified tokens in the text) may then be identified as hypotheses for the medical fact to be extracted from that portion of the text. Exemplary techniques that may be used in some embodiments are described in Salton, Wong, & Yang: “A vector space model for automatic indexing,” Communications of the ACM, November 1975. This publication is incorporated herein by reference in its entirety. However, these are merely examples, and any suitable technique(s) for normalizing entity tokens to standard terms may be utilized in some embodiments, as aspects of the invention are not limited in this respect.

In some embodiments, the normalization/coding process may output a single hypothesis for the standard form and/or code corresponding to each extracted fact. For example, the single output hypothesis may correspond to the concept linked in the ontology to the term that is most similar to the token(s) in the text from which the fact is extracted. However, in other embodiments, the normalization/coding process may output multiple alternative hypotheses, e.g., with corresponding probabilities, for the standard form and/or code corresponding to an individual extracted fact. Thus, it should be appreciated that in some embodiments multiple alternative hypotheses for a medical fact to be extracted from a portion of input text may be identified by fact extraction component 104. Such alternative hypotheses may be collected at any or all of various processing levels of fact extraction, including entity detection, entity relation, and/or normalization/coding stages. In some embodiments, the list of alternative hypotheses may be thresholded at any of the various levels, such that the final list output by fact extraction component 104 may represent the N-best alternative hypotheses for a particular medical fact to be extracted.

It should be appreciated that the foregoing are merely examples, and that fact extraction component 104 may be implemented in any suitable way and/or form, as aspects of the invention are not limited in this respect.

As discussed above, in accordance with one embodiment, a free-form narration of a patient encounter, narrated by a clinician, is processed by a fact extraction component that includes a natural language understanding (NLU) engine capable of extracting one or more clinical facts corresponding to the mention of an orderable item, and is capable of distinguishing between whether the one or more clinical facts indicate an intent to order the orderable item or not. In response to determining that the one or more clinical facts indicate an intent to order the orderable item, an order for the item can be automatically generated. The aspect of the present invention related to determining an intent to order an orderable item can be implemented using any of the techniques described herein for performing fact extraction and/or for understanding a free-form narration. However, it should be appreciated that this aspect of the present invention is not limited to any particular implementation technique, and can be implemented in any suitable manner.

As discussed above, it is often the case that during the course of a clinical encounter, or at some point thereafter, a clinician may document the patient encounter via a free-form narration. Such a narration may often include a number of orderable items. Examples of such orderable items include in-patient orders for medication in a clinical facility (e.g., a hospital) and out-patient medication orders (e.g., prescriptions), orders for clinical procedures (e.g., an MRI, a CT scan or any of numerous other types of procedures), orders for laboratory work or other tests, scheduling follow-up appointments and referrals to other clinicians (e.g., other physicians or specialists, physical therapy, etc.), communication orders (e.g., orders for instructions, counseling, guidance or training for any of numerous topics such as smoking cessation or dietary counseling), etc. In accordance with some embodiments described herein, a free-form narration of a clinical encounter can be processed using an NLU engine to extract one or more clinical facts relating to the mention of an orderable item, the processing can distinguish between whether the narration indicates an intent to order the orderable item or not, and when an intent to order is determined, an order for the orderable item can be generated.

It should be appreciated that using conventional systems, the generation of an order referenced in a narration of a patient encounter is a manual process. That is, in addition to referencing the orderable item in the narration that results from the clinical encounter, the clinician or another individual (e.g., a clinician's assistant) needs to take additional explicit action to generate any orders for orderable items mentioned in the narration. In accordance with some embodiments described herein, the documentation of the clinical encounter can automatically drive the workflows in the clinical environment and automatically result in generation of an order for any orderable items that the clinician expresses a desire to order in the narration documenting the clinical encounter. This provides efficiency and accuracy benefits, as automating the order generation process ensures that any parameters for the orderable item mentioned in the narration are accurately specified in the generated order.

In some embodiments, an order may be automatically generated, but may not be dispatched to a fulfillment system until a clinician or other authorized individual reviews the generated order and confirms that it is accurate or otherwise signs off on it to move the order to the fulfillment system. In addition, if the documentation of the clinical counter does not fully specify all of the parameters for an orderable item, in accordance with some embodiments, any missing parameters can be highlighted in the generated order to facilitate the clinician fully specifying the orderable item before it is dispatched to the fulfillment system. It should be appreciated that there are no limitations on the techniques described herein that require authorization before an order is dispatched. Therefore, if the procedures of the health care organization allow, in some embodiments, the generated order may be automatically dispatched, using any suitable order fulfillment system applicable to the orderable item, examples of which are discussed below.

As mentioned above, the techniques described herein can be used with any orderable item. Some examples of orderable items and illustrative parameters for specifying those orderable items will now be described. However, it should be appreciated that this list is illustrative and not exhaustive, as the techniques described herein can be used in connection with any orderable item, and are not limited to use with the examples of orderable items described herein, nor to the illustrative parameters described for any of the illustrative orderable items mentioned.

One example of an orderable item is a medication, which may involve an in-patient or out-patient order. Examples of parameters for ordering a medication may include the name of the medication (e.g., a commercial medication or drug name or a generic name), a dose, a route, a frequency, a duration and an indication (e.g., specifying a symptom, condition, disease, etc. that indicates that the medication should be taken).

Another example of an orderable item is a procedure. The parameters for a procedure typically include an identification of the type of the procedure, as well as a location and date for the procedure. Typically, the location and date for the procedure are not specified in the clinician's narration of the patient encounter, and may be included in the task of scheduling the procedure.

Another example of an orderable action item is a laboratory procedure for tests. Typical parameters for a laboratory procedure or test include an identification of the type of procedure or test, a date, a frequency if it is to be repeated, and any special instructions.

Another example of an orderable item is a communication order, which may be an order for instructions, counseling, guidance, training, etc. The parameters may vary depending upon the nature of the communication order and whether it is to be given verbally or via some reference materials (e.g., written leaflets or other material to be provided to the patient).

Another example of an orderable item relates to follow-up visits with a clinician. The parameters for a follow-up visit typically include information identifying the type of visit (e.g., is it a special purpose visit to address something in particular, a general check-up, etc.), a date and any special instructions. As with procedures, the date may or may not be specified in the clinician's narration, and may alternatively be part of the task of scheduling the follow-up visit.

Some non-limiting examples of orderable items and non-limiting examples of the manner in which they may be expressed by a clinician's free-form narration include:

-   -   a. Medications: Tylenol 650 mg two tablets every 6 hours as         needed; Caduet q h.s., 25 mg of atenolol twice daily; Compazine         2-3 times daily as needed for nausea;     -   b. Radiology: CT scan chest and neck, with co;     -   c. Labs: full blood panel, with RBC and WBC count and urine         test, 12 hours fasting;     -   d. Biopsy: ultrasound guided biopsy for kidney mass and         surrounding lymph nodes; and     -   e. Follow up: patient is advised to come back in two weeks for         follow-up on his [disease name]

In accordance with some embodiments described herein, the fact extraction component employs an NLU engine that has the capability of determining whether an orderable item referenced in the free-form narration is referenced in a manner indicating an intent by the clinician to order the orderable item or not, so that the system distinguishes between whether the at least one clinical fact extracted from the free-form narration indicates an intent to order the orderable item or not. In this respect, it should be appreciated that every reference to an item that may be orderable (e.g., a medication, a clinical procedure, a lab or test, etc.) in a free-form narration may not be mentioned in the context of an intent to order the item. As one example, the documentation of a clinical encounter may document that a patient is already taking a particular medication, or may have already undergone a particular procedure, so that the reference to the medication or procedure does not evidence an intent by the clinician to order that item for the patient. While in some embodiments an order may be generated for all orderable items referenced in the documentation of the clinical encounter without determining whether the clinician intended to order it, in other embodiments such a determination is made to minimize the generation of orders that are not intended or wanted.

The extraction of at least one clinical fact that corresponds to the mention of an orderable item and indicates an intent to order the orderable item or not can be implemented in any suitable manner. In accordance with one embodiment, the fact extraction component described above can be used. In accordance with one embodiment, facts that may be extracted by the system relating to an orderable item may include an attribute indicating whether the narration from which the fact is extracted indicates an intent to order the orderable item or not. In some embodiments, the attributes relating to an orderable item can specify whether the narration includes a current intent to order the orderable item, whether the narration does not evidence an intent to order the orderable item but that the item is currently relevant for the patient, or whether the orderable item is referenced in the narration in a manner that does not evidence an intent to order the item and references it in a non-current way (e.g., as a historical reference, as a family history reference, etc.). For the example of a medication, the fact extraction component may extract medication facts with a label that indicates whether the narration evidences an intent to order the medication, whether the medication is referenced as something the patient is already taking, or whether the history of the patient indicates that the patient previously took the medication but is not currently doing so. It should be appreciated that the reference to other types of attributes in addition to an attribute indicating whether the narration evidences an intent to order the orderable item are merely illustrative, as all embodiments described herein are not limited to use with such additional attributes. The fact extraction component can determine whether the narration evidences an intent to order the orderable item in any of numerous ways, as the aspects of the present invention described herein are not limited to any particular implementation technique. As discussed above, in accordance with one embodiment of the present invention, the intent need not be expressed in any fixed or specific manner, as aspects of the present invention are designed to determine such an intent from a free-form narration that can take any form. It should be appreciated that there are numerous ways in which a clinician can express an intent to order an orderable item, and that different expressions may typically be used for different types of actionable orders. Some non-limiting examples of expressions a clinician may use to express an intent to order various types of orderable items include:

-   -   a. “I will start [drug name] [dosage and frequency] for his         [disease name] to be taken before bed for [duration] . . . ”     -   b. “start a cycle of [drug name] [dosage and frequency] . . . ”     -   c. “patient should see Dr. [dr. name] to follow-up on his         [disease name]”     -   d. “patient is scheduled for a follow-up in this clinic for         [reason for follow-up]”     -   e. “I will consult with Dr. [dr. name] to plan for a [procedure         name]”

In accordance with some embodiments, the aspects of the present invention that relate to generating an order may process a clinician's narrative documentation in real-time. However, it should be appreciated that all aspects of the present invention are not limited in this respect, and that the processing of the narration can alternatively be performed at any later time, rather than in real-time so that the order need not be generated during a session in which the clinician is interacting with the system to which the narration is input.

In addition to the examples provided above, it should further be appreciated that in some circumstances the free-form narration of the patient encounter may include language that structures the narration and provides an indication of an intent to order. For example, if the narration includes language indicating that the clinician is now providing a “plan” or other similar language, it may indicate an intent to order any subsequently referenced orderable items.

As discussed above, in some embodiments, the fact extraction component and the NLU engine included therein may employ a statistical model that can be used to extract facts, including facts and/or attributes thereof indicating an intent to order an orderable item. The statistical model can take any suitable form and be trained in any suitable way. As one non-limiting example, the model may be trained using a corpus of hand-labeled training data with examples of references to an orderable item in both contexts where an intent to order is expressed and others where an intent to order is not expressed. Non-limiting examples of the ways in which a statistical model can be trained are described above.

In other embodiments, the NLU engine of the fact extraction component may include a rule-based natural language processing system. As discussed above, in a rule-based system, a linguist and/or other individual may create a plurality of rules that can specify what words or combinations or words evidence an intent to order an orderable item and/or what words or combinations of words do not. Examples of a rule-based system are described above, and those techniques can be employed to develop an NLU engine capable of detecting an intent (or not) to order an orderable item. However, it should be appreciated that the techniques described herein are not limited to any particular techniques for developing a rule-based natural language understanding component.

Some examples of language that the CLU system may detect as evidencing an intent to order a number of different types of orderable items were described above. It should be appreciated that one or more rules can be written to detect each of these examples (and/or others) of language that illustrate an intent to order an orderable item. As another example, consider the narrative “I'm starting this patient on beta-blockers. Propofol 2 mg/day.” The reference to “I'm starting” is an indication of an intent to order the medication. An example of a rule that may detect this intent is a rule that detects a forward-looking verb (e.g., “starting”) within a specified proximity (e.g., 5-10 words) of a medication, which can be identified using the fact extraction techniques described above. Of course, this is merely an example. Any suitable rule can be established, as the aspects of the present invention described herein are not limited to any particular types of rules.

In accordance with one embodiment described herein, a hybrid approach is used in which the NLU engine of the fact extraction component employs both a statistical model and a rules-based component to distinguish between whether a narration indicates an intent to order an orderable item or not. The hybrid approach can be implemented in any of numerous ways, as the aspect of the present invention that employs a hybrid approach is not limited to any particular implementation technique. In accordance with one embodiment, the statistic model and rules-based component of the NLU engine may be executed in parallel on the same text of the narration, and the identification of an intent to order an orderable item may only be triggered when there is mutual agreement between these two components.

In an alternate embodiment, a rules-based component may perform a first pass on the narration to segment it into sections and identify sections that are likely to include orderable items. For example, as discussed above, some narrations may include a “plan” or “order” section that is likely to include orderable items, whereas some other sections (e.g., discussing medical history) may not. Thereafter, the statistical model may be used to process the text in the sections identified as likely to include orderable items. In some embodiments, prior to running the statistical model, the rules-based component may further operate upon the sections of text identified as likely to include orderable items and may divide those sections of the text into sentences, and the statistical model may then be run on each sentence to identify orderable items and determine whether an intent is expressed to order any orderable item or not. In yet a further alternative, after the statistical model has been operated on each of the sentences in the sections of text identified as likely to include an orderable item, the rules-based component can be applied again to find contextual information that may add additional attributes or otherwise provide contextual information for a fact extracted by the statistical model, wherein the rules-based component may review other text in the narration beyond the sentence operated upon by the statistical model to extract the fact.

In accordance with another embodiment of the present invention, a determination can be made about whether to use the statistical model or the rule-based component depending upon the type of the orderable item. For example, some facts that are very structured (e.g., dates) may lend themselves to rules, whereas types of facts with significant variability in how they are expressed in natural language (e.g., procedures) may be better suited to the use of a statistical model.

In accordance with some embodiments, an ontology of the type described can be used in conjunction with the statistical model in any of numerous ways, examples of which are described above. As one non-limiting example, the use of an ontology can reduce the amount of annotated data that can be used in training the statistical model, as the ontology can demonstrate a number of alternate ways of expressing the same fact or concept. Thus, it may not be necessary to include annotated data representing all of the alternate expressions for a common fact or concept, as the model can be trained to detect a limited number of these (e.g., a single one) and the ontology can be combined with the statistical model to expand its ability to recognize alternative expressions not included in the annotated training data. Of course, this is merely one use of an ontology, as the ontology can be used in any suitable manner.

In yet a further embodiment, the outputs of the rules-based component can be used as features for the statistical model. For example, when a rule fires or otherwise indicates that the rule has been met, this may be a feature evaluated by the statistical model. Some rules may be quite specific, so that a firing of the rule indicates with high probability that the determination expressed thereby (e.g., whether an intent to order an orderable item has been expressed or not) can be quite accurate.

Again, the descriptions provided above for combining the use of a rule-based component with a statistical model and an ontology are merely illustrative, as the techniques described herein are not limited to any particular implementation techniques. The techniques described herein can be implemented using solely a statistical model, solely a rule-based component, or any combination, as they are not limited to any particular implementation technique.

It should be appreciated that the reference to the statistical model and/or rules-based component that determines whether an intent to order an orderable item has been expressed can be considered to be an intent classifier. It should be appreciated that the features considered by the intent classifier are not limited to clinical facts of the types discussed above, and can include numerous other types of features, including linguistic features that may exam document structure (e.g., the reference to a “plan” above), sentence structure, particular words, the tense of a word, conditionals, etc. As discussed above, one of these features is temporal. For example, mentions of a medication in past medical history or on a current medication list do not express an intent to order the medication, but a mention in a plan section of a narration would. Similarly, a mention of a medication in a family history or, for example, “a past patient with a similar diagnosis responded well to [medication]” is not an indication of an intent to order the medication. In addition, negation may also be a feature that may be considered in some embodiments. For example, “I am not going to put this patient on [medication] again” is not an indication of an intent to order the medication. Similarly, a hedge or reference to the ordering of an orderable item as a possibility that is being considered but that has not yet been decided upon (“maybe we should prescribe [medication] to this patient”) is not an indication of an intent to order the medication.

In accordance with some embodiments, information extracted from a narration to generate an order for an orderable item can include default and/or implied values for fields in the order for the orderable item. For example, if the narration mentions a “IV,” (i.e., the medical route intravenous), this implies that the medication should be administered in a liquid form, which may be a field of the order form for the medication, so that in some embodiments described herein, the liquid form can be included in the order for the medication because it is implied. As another example, if the narration indicates that medication should be administered “stat,” this implies that the medication needs to be administered within the next 15 minutes, which may enable the start time field in an order form for the medication to be populated. The capability to populate default and/or implied field values can be implemented through the use of clinical knowledge rules, or in any other suitable manner.

In accordance with some embodiments, the fact extraction component may be integrated with downstream clinical systems that receive an order for the orderable item. The systems can include, for example, clinical order entering systems, scheduling systems, etc. As one non-limiting example, industry standard electronic interfaces can be used to connect with such downstream clinical systems. For example, the order may be presented as an electronic message in accordance with the HL7 standard or in any other suitable manner. Examples of industry standard electronic interfaces include ePrescribing or CPOE for prescriptions, the CPOE system for ordering procedures, and any of numerous systems for ordering labs, order management scheduling systems, etc.

In accordance with some embodiments, one or more coding systems can be used that facilitates the placing of an order in its proper form. Such systems can be used to normalize terminology and/or provide one or more codes for an orderable item that may be required by the ordering system. For example, a medication with a name “X” may be orderable in a particular ordering system only by using a different name or code “Z”. A coding system may use one or more coding standards (e.g., RxNorm for medications, LOINC for laboratory and diagnostic orders, etc.).

In accordance with some embodiments, the system that generates an order for an orderable item may also perform some analysis to detect and provide an alert for potential errors and/or missing information. This can be performed in any suitable manner, examples of which were discussed above. For example, when the orderable item is a medication, the dosage may be checked to determine if it is between a minimum and maximum range, and/or its form and route may be checked for consistency. As an another example, recent laboratory results for the patient may be checked to ensure that the medication is compatible with them (e.g., the patient's cholesterol level). As another example, drug interactions may be checked to ensure that the medication being ordered is compatible with medications on the patient's current medication list. As yet another example, a check may be made for a medication to ensure that it is compatible with any allergies in the patient's medical history. These determinations can be performed in any suitable manner, including using one or more clinical support systems that include information about the suitability and compatibility of dosages, forms and routes of medication, compatibility between different types of medication, compatibility of medications with particular allergies, etc.

In some embodiments, a user such as clinician 120 may monitor, control and/or otherwise interact with the fact review process through a user interface provided in connection with system 100. For example, in some embodiments, user interface 140 may be provided by fact review component 106, e.g., through execution (e.g., by one or more processors of system 100) of programming instructions incorporated in fact review component 106. One exemplary implementation of such a user interface is graphical user interface (GUI) 200, illustrated in FIG. 2. In some embodiments, when the user is clinician 120, GUI 200 may be presented via user interface 110. In some embodiments, a user may be a person other than a clinician; for example, another person such as coding specialist 150 may be presented with GUI 200 via user interface 140. However, it should be appreciated that “user,” as used herein, refers to an end user of system 100, as opposed to a software and/or hardware developer of any component of system 100.

The user interface is not limited to a graphical user interface, as other ways of providing data from system 100 to users may be used. For example, in some embodiments, audio indicators may be transmitted from system 100 and conveyed to a user. It should be appreciated that any type of user interface may be provided in connection with fact extraction, fact review and/or other related processes, as aspects of the invention are not limited in this respect. While the exemplary embodiments illustrated in FIG. 1 involve data processing at system 100 and data communication between system 100 and user interfaces 110 and/or 140, it should be appreciated that in other embodiments any or all processing components of system 100 may instead be implemented locally at user interface 110 and/or user interface 140, as aspects of the invention are not limited to any particular distribution of local and/or remote processing capabilities.

As depicted in FIG. 2, GUI 200 includes a number of separate panes displaying different types of data. Identifying information pane 210 includes general information identifying patient 222 as a male patient named John Doe. Such general patient identifying information may be entered by clinician 120, or by other user 150, or may be automatically populated from an electronic medical record for patient 122, or may be obtained from any other suitable source. Identifying information pane 210 also displays the creation date and document type of the report currently being worked on. This information may also be obtained from any suitable source, such as from stored data or by manual entry. When referring herein to entry of data by clinician 120 and/or other user 150, it should be appreciated that any suitable form of data entry may be used, including input via mouse, keyboard, touchscreen, stylus, voice, or any other suitable input form, as aspects of the invention are not limited in this respect.

GUI 200 as depicted in FIG. 2 includes a text panel 220 in which a text narrative referring to the encounter between clinician 120 and patient 122 is displayed. In some embodiments, text panel 220 may include text editor functionality, such that clinician 120 may directly enter the text narrative into text panel 220, either during the patient encounter or at some time thereafter. If ASR is used to produce the text narrative from a spoken dictation provided by clinician 120, in some embodiments the text may be displayed in text panel 220 as it is produced by ASR engine 102, either in real time while clinician 120 is dictating, or with a larger processing delay. In other embodiments, the text narrative may be received as stored data from another source, such as from medical transcriptionist 130, and may be displayed in completed form in text panel 220. In some embodiments, the text narrative may then be edited if desired by clinician 120 and/or other user 150 within text panel 220. However, text editing capability is not required, and in some embodiments text panel 220 may simply display the text narrative without providing the ability to edit it.

Exemplary GUI 200 further includes a fact panel 230 in which one or more medical facts, once extracted from the text narrative and/or entered in another suitable way, may be displayed as discrete structured data items. When clinician 120 and/or other user 150 is ready to direct fact extraction component 104 to extract one or more medical facts from the text narrative, in some embodiments he or she may select process button 240 via any suitable selection input method. However, a user indication to begin fact extraction is not limited to a button such as process button 240, as any suitable way to make such an indication may be provided by GUI 200. In some embodiments, no user indication to begin fact extraction may be required, and fact extraction component 104 may begin a fact extraction process as soon as a requisite amount of text (e.g., enough text for fact extraction component 104 to identify one or more clinical facts that can be ascertained therefrom) is entered and/or received. In some embodiments, a user may select process button 240 to cause fact extraction to be performed before the text narrative is complete. For example, clinician 120 may dictate, enter via manual input and/or otherwise provide a part of the text narrative, select process button 240 to have one or more facts extracted from that part of the text narrative, and then continue to provide further part(s) of the text narrative. In another example, clinician 120 may provide all or part of the text narrative, select process button 240 and review the resulting extracted facts, edit the text narrative within text pane 220, and then select process button 240 again to review how the extracted facts may change.

In some embodiments, one or more medical facts extracted from the text narrative by fact extraction component 104 may be displayed to the user via GUI 200 in fact panel 230. Screenshots illustrating an example display of medical facts extracted from an example text narrative are provided in FIGS. 3A and 3B. FIG. 3A is a screenshot with fact panel 230 scrolled to the top of a display listing medical facts extracted from the example text narrative, and FIG. 3B is a screenshot with fact panel 230 scrolled to the bottom of the display listing the extracted medical facts. In some embodiments, as depicted in FIGS. 3A and 3B, medical facts corresponding to a patient encounter may be displayed in fact panel 230, and organized into a number of separate categories of types of facts. An exemplary set of medical fact categories includes categories for problems, medications, allergies, social history, procedures and vital signs. However, it should be appreciated that any suitable fact categories may be used, as aspects of the invention are not limited in this respect. In addition, organization of facts into categories is not required, and displays without such organization are possible. As depicted in FIGS. 3A and 3B, in some embodiments GUI 200 may be configured to provide a navigation panel 300, with a selectable indication of each fact category available in the display of fact panel 230. In some embodiments, when the user selects one of the categories within navigation panel 300 (e.g., by clicking on it with a mouse, touchpad, stylus, or other input device), fact panel 230 may be scrolled to display the corresponding fact category. As depicted in FIGS. 3A and 3B, all available fact categories for the current document type are displayed, even if a particular fact category includes no extracted or otherwise entered medical facts. However, this is not required; in some embodiments, only those fact categories having facts ascertained from the patient encounter may be displayed in fact panel 230.

Fact panel 230 scrolled to the top of the display as depicted in FIG. 3A shows problem fact category 310, medications fact category 320, and allergies fact category 330. Within problem fact category 310, four clinical facts have been extracted from the example text narrative; no clinical facts have been extracted in medications fact category 320 or in allergies fact category 330. Within problem fact category 310, fact 312 indicates that patient 122 is currently presenting with unspecified chest pain; that the chest pain is a currently presenting condition is indicated by the status “active”. Fact 314 indicates that patient 122 is currently presenting with shortness of breath. Fact 316 indicates that the patient has a history (status “history”) of unspecified essential hypertension. Fact 318 indicates that the patient has a history of unspecified obesity. As illustrated in FIG. 3A, each clinical fact in problem fact category 310 has a name field and a status field. In some embodiments, each field of a clinical fact may be a structured component of that fact represented as a discrete structured data item. In this example, the name field may be structured such that only a standard set of medical terms for problems may be available to populate that field. For example, the status field may be structured such that only statuses in the Systematized Nomenclature of Medicine (SNOMED) standard (e.g., “active” and “history”) may be selected within that field, although other standards (or no standard) could be employed. An exemplary list of fact categories and their component fields is given below. However, it should be appreciated that this list is provided by way of example only, as aspects of the invention are not limited to any particular organizational system for facts, fact categories and/or fact components.

Exemplary List of Fact Categories and Component Fields

Category: Problems. Fields: Name, SNOMED status, ICD code.

Category: Medications. Fields: Name, Status, Dose form, Frequency, Measures, RxNorm code, Administration condition, Application duration, Dose route.

Category: Allergies. Fields: Allergen name, Type, Status, SNOMED code, Allergic reaction, Allergen RxNorm.

Category: Social history—Tobacco use. Fields: Name, Substance, Form, Status, Qualifier, Frequency, Duration, Quantity, Unit type, Duration measure, Occurrence, SNOMED code, Norm value, Value.

Category: Social history—Alcohol use. Fields: Name, Substance, Form, Status, Qualifier, Frequency, Duration, Quantity, Quantifier, Unit type, Duration measure, Occurrence, SNOMED code, Norm value, Value.

Category: Procedures. Fields: Name, Date, SNOMED code.

Category: Vital signs. Fields: Name, Measure, Unit, Unit type, Date/Time, SNOMED code, Norm value, Value.

In some embodiments, a linkage may be maintained between one or more medical facts extracted by fact extraction component 104 and the portion(s) of the text narrative from which they were extracted. As discussed above, such a portion of the text narrative may consist of a single word or may include multiple words, which may be in a contiguous sequence or may be separated from each other by one or more intervening words, sentence boundaries, section boundaries, or the like. For example, fact 312 indicating that patient 122 is currently presenting with unspecified chest pain may have been extracted by fact extraction component 104 from the words “chest pain” in the text narrative. The “active” status of extracted fact 312 may have been determined by fact extraction component 104 based on the appearance of the words “chest pain” in the section of the text narrative with the section heading “Chief complaint”. In some embodiments, fact extraction component 104 and/or another processing component may be programmed to maintain (e.g., by storing appropriate data) a linkage between an extracted fact (e.g., fact 312) and the corresponding text portion (e.g., “chest pain”).

In some embodiments, GUI 200 may be configured to provide visual indicators of the linkage between one or more facts displayed in fact panel 230 and the corresponding portion(s) of the text narrative in text panel 220 from which they were extracted. In the example depicted in FIG. 3A, the visual indicators are graphical indicators consisting of lines placed under the appropriate portions of the text narrative in text panel 220. Indicator 313 indicates the linkage between fact 312 and the words “chest pain” in the “Chief complaint” section of the text narrative; indicator 315 indicates the linkage between fact 314 and the words “shortness of breath” in the “Chief complaint” section of the text narrative; indicator 317 indicates the linkage between fact 316 and the word “hypertensive” in the “Medical history” section of the text narrative; and indicator 319 indicates the linkage between fact 318 and the word “obese” in the “Medical history” section of the text narrative. However, these are merely examples of one way in which visual indicators may be provided, as other types of visual indicators may be provided. For example, different or additional types of graphical indicators may be provided, and/or linked text in text panel 220 may be displayed in a distinctive textual style (e.g., font, size, color, formatting, etc.). Aspects of the invention are not limited to any particular type of linkage indicator.

In some embodiments, when the textual representation of the free-form narration provided by clinician 120 has been re-formatted and fact extraction has been performed with reference to the re-formatted version, the original version may nevertheless be displayed in text panel 220, and linkages may be maintained and/or displayed with respect to the original version. For example, in some embodiments, each extracted clinical fact may be extracted by fact extraction component 104 from a corresponding portion of the re-formatted text, but that portion of the re-formatted text may have a corresponding portion of the original text of which it is a formatted version. A linkage may therefore be maintained between that portion of the original text and the extracted fact, despite the fact actually having been extracted from the re-formatted text. In some embodiments, providing an indicator of the linkage between the extracted fact and the original text may allow clinician 120 and/or other user 150 to appreciate how the extracted fact is related to what was actually said in the free-form narration. However, other embodiments may maintain linkages between extracted facts and the re-formatted text, as an alternative or in addition to the linkages between the extracted facts and the original text, as aspects of the invention are not limited in this respect.

Fact panel 230 scrolled to the bottom of the display as depicted in FIG. 3B shows social history fact category 340, procedures fact category 350, and vital signs fact category 360. Within social history fact category 340, two clinical facts have been extracted; no facts have been extracted in procedures fact category 350 and vital signs fact category 360. Within social history fact category 340, fact 342 indicates that patient 122 currently smokes cigarettes with a frequency of one pack per day. Fact 344 indicates that patient 122 currently occasionally drinks alcohol. Indicator 343 indicates that fact 342 was extracted from the words “He smokes one pack per day” in the “Social history” section of the text narrative; and indicator 345 indicates that fact 344 was extracted from the words “Drinks occasionally” in the “Social history” section of the text narrative. In some embodiments, visual indicators such as indicators 343 and 345 may be of a different textual and/or graphical style or of a different indicator type than visual indicators such as indicators 313, 315, 317 and 319, to indicate that they correspond to a different fact category. For example, in some embodiments indicators 343 and 345 corresponding to social history fact category 340 may be displayed in a different color than indicators 313, 315, 317 and 319 corresponding to problems fact category 310. In some embodiments, linkages for different individual facts may be displayed in different textual and/or graphical styles or indicator types to allow the user to easily appreciate which fact corresponds to which portion of the text narrative. For example, in some embodiments indicator 343 may be displayed in a different color than indicator 345 because they correspond to different facts, even though both correspond to the same fact category.

In some embodiments, GUI 200 may be configured to allow the user to select one or more of the medical facts in fact panel 230, and in response to the selection, to provide an indication of the portion(s) of the text narrative from which those fact(s) were extracted. An example is illustrated in FIG. 4. In this example, fact 312 (“unspecified chest pain”) has been selected by the user in fact panel 230, and in response visual indicator 420 of the portion of the text narrative from which fact 312 was extracted (“chest pain”) is provided. Such a user selection may be made in any suitable way, as aspects of the invention are not limited in this respect. Examples include using an input device (e.g., mouse, keyboard, touchpad, stylus, etc.) to click on or otherwise select fact 312, hovering the mouse or other input mechanism above or nearby to fact 312, speaking a selection of fact 312 through voice, and/or any other suitable selection method. Similarly, in some embodiments GUI 200 may be configured to visually indicate the corresponding fact in fact panel 230 when the user selects a portion of the text narrative in text panel 220. In some embodiments, a visual indicator may include a line or other graphical connector between a fact and its corresponding portion of the text narrative. Any visual indicator may be provided in any suitable form (examples of which are given above) as aspects of the invention are not limited in this respect. In addition, aspects of the invention are not limited to visual indicators, as other forms of indicators may be provided. For example, in response to a user selection of fact 312, an audio indicator of the text portion “chest pain” may be provided in some embodiments. In some embodiments, the audio indicator may be provided by playing the portion of the audio recording of the clinician's spoken dictation comprising the words “chest pain”. In other embodiments, the audio indicator may be provided by playing an audio version of the words “chest pain” generated using automatic speech synthesis. Any suitable form of indicator or technique for providing indicators may be used, as aspects of the invention are not limited in this respect.

In some embodiments, GUI 200 may be configured to provide any of various ways for the user to make one or more changes to the set of medical facts extracted from the text narrative by fact extraction component 104 and displayed in fact panel 230. For example, the user may be allowed to delete a fact from the set in fact panel 230, e.g., by selecting the “X” option appearing next to the fact. In some embodiments, the user may be allowed to edit a fact within fact panel 230. In one example, the user may edit the name field of fact 312 by selecting the fact and typing, speaking or otherwise providing a different name for that fact. As depicted in FIG. 3A and FIG. 4, in some embodiments the user may edit the status field of fact 312 by selecting a different status from the available drop-down menu, although other techniques for allowing editing of the status field are possible. In some embodiments, the user may alternatively or additionally be allowed to edit a fact by interacting with the text narrative in text panel 220. For example, the user may add, delete, or change one or more words in the text narrative, and then the text narrative may be re-processed by fact extraction component 104 to extract an updated set of medical facts. In some embodiments, the user may be allowed to select only a part of the text narrative in text panel 220 (e.g., by highlighting it), and have fact extraction component 104 re-extract facts only from that part, without disturbing facts already extracted from other parts of the text narrative.

In some embodiments, GUI 200 may be configured to provide any of various ways for one or more facts to be added as discrete structured data items. As depicted in FIG. 4, GUI 200 in some embodiments may be configured to provide an add fact button for each fact category appearing in fact panel 230; one such add fact button is add fact button 430. When the user selects add fact button 430, in some embodiments GUI 200 may provide the user with a way to enter information sufficient to populate one or more fields of a new fact in that fact category, for example by displaying pop-up window 500 as depicted in FIG. 5. It should be appreciated that this is merely one example, as aspects of the invention are not limited to the use of pop-up windows or any other particular method for adding a fact. In this example, pop-up window 500 includes a title bar 510 that indicates the fact category (“Problems”) to which the new fact will be added. Pop-up window 500 also provides a number of fields 520 in which the user may enter information to define the new fact to be added. Fields 520 may be implemented in any suitable form, including as text entry boxes, drop-down menus, radio buttons and/or checkboxes, as aspects of the invention are not limited to any particular way of receiving input defining a fact. Finally, pop-up window 500 includes add button 530, which the user may select to add the newly defined fact to the set of facts corresponding to the patient encounter, thus entering the fact as a discrete structured data item.

In some embodiments, GUI 200 may alternatively or additionally be configured to allow the user to add a new fact by selecting a (not necessarily contiguous) portion of the text narrative in text panel 220, and indicating that a new fact should be added based on that portion of the text narrative. This may be done in any suitable way. In one example, the user may highlight the desired portion of the text narrative in text panel 220, and right-click on it with a mouse (or perform another suitable input operation), which may cause the designated text to be processed and any relevant facts to be extracted. In other embodiments, the right-click or other input operation may cause a menu to appear. In some embodiments the menu may include options to add the new fact under any of the available fact categories, and the user may select one of the options to indicate which fact category will correspond to the new fact. In some embodiments, an input screen such as pop-up window 500 may then be provided, and the name field may be populated with the words selected by the user from the text narrative. The user may then have the option to further define the fact through one or more of the other available fields, and to add the fact to the set of medical facts for the patient encounter as described above.

In some embodiments, the set of medical facts corresponding to the current patient encounter (each of which may have been extracted from the text narrative or provided by the user as a discrete structured data item) may be added to an existing electronic medical record (such as an EHR) for patient 122, or may be used in generating a new electronic medical record for patient 122. In some embodiments, clinician 120 and/or coding specialist (or other user) 150 may finally approve the set of medical facts before they are included in any patient record; however, aspects of the present invention are not limited in this respect. In some embodiments, when there is a linkage between a fact in the set and a portion of the text narrative, the linkage may be maintained when the fact is included in the electronic medical record. In some embodiments, this linkage may be made viewable by simultaneously displaying the fact within the electronic medical record and the text narrative (or at least the portion of the text narrative from which the fact was extracted), and providing an indication of the linkage in any of the ways described above. Similarly, extracted facts may be included in other types of patient records, and linkages between the facts in the patient records and the portions of text narratives from which they were extracted may be maintained and indicated in any suitable way.

In some embodiments, one or more medical facts, either automatically extracted from a text narrative by fact extraction component 104 or directly entered by a user as discrete structured data items, may be input to fact review component 106 for automatic review. In some embodiments, fact review component 106 may be programmed to identify opportunities for the medical documentation of the patient encounter to be improved, and if any such opportunities are identified, to provide an alert to the user (e.g., clinician 120 or other user 150). Some examples of alerts that may be provided are described above. As discussed, any suitable form of alert, including visual and/or audio alerts, may be used, as aspects of the invention are not limited in this respect. In some embodiments, the review of collected medical facts to determine opportunities for improved medical documentation, and the resulting alerting and/or querying of the user, may be performed entirely automatically by fact review component 106 or any other suitable component. As used herein, performing a process “automatically” refers to having no required human participation between the input to the process and its corresponding output, with all intervening acts performed by machine.

As discussed above, one type of alert that may be provided to a user by fact review component 106 is an alert of a potential opportunity to increase the specificity of the set of facts ascertained from the patient encounter. This can be done in any suitable way. In some embodiments, fact review component may be programmed with a set of deterministic rules to decide when such a potential opportunity exists. For example, in some embodiments, if a clinical term corresponding to one of the facts is linked to a concept in the formal ontology used by fact extraction component 104, and that concept is a parent to one or more specific child concepts in the ontology, then fact review component 106 may generate an alert to query the user as to whether one of the more specific child concepts can actually be ascertained from the patient encounter. If the user answers in the affirmative, in some embodiments fact review component 106 may cause the more general fact to be replaced by a more specific version indicated by the user. Similarly, if one or more concepts in the formal ontology are linked to clinical terms appearing in the set of facts, and if those concepts have relationships in the ontology to a fact that could add specificity to the set of facts, and alert and/or query may be generated. As an example, if one or more conditions documented in the set of facts are known through ontological relationships to be symptoms of a specific diagnosis, in some embodiments fact review component 106 may query clinician 120 or other user 150 as to whether the specific diagnosis may be ascertained from the patient encounter and added to the facts. In some embodiments, as an alternative or in addition to the set of deterministic rules, a statistical model may be used to identify situations in which a potential opportunity to increase the specificity of the set of facts exists.

In another example, one or more of the facts in the set collected (either by fact extraction from a text narrative or by direct entry as one or more discrete structured data items) from the patent encounter may correspond to one or more standard codes used for billing, ordering, evaluating quality of care, or the like. Such standard codes may be specific to the healthcare institution or may be a standard shared by multiple institutions. Examples of such standard coding systems include, but are not limited to, ICD codes, CPT (Current Procedural Terminology) codes, E&M (Evaluation and Management) codes, MedDRA (Medical Dictionary for Regulatory Activities) codes, SNOMED codes, LOINC (Logical Observation Identifiers Names and Codes) codes, RxNorm codes, NDC (National Drug Code) codes and RadLex codes. Some such standard coding systems are hierarchical, in that certain codes within the system are more specific versions of other codes within the system. For example, in the ICD-10 coding system, code I20 represents “angina pectoris” (chest pain due to lack of blood and oxygen to the heart muscle). More specific versions of ICD-10 code I20 include I20.0 (“unstable angina”), I20.1 (“angina pectoris with documented spasm”), I20.8 (“other forms of angina pectoris”) and I20.9 (“angina pectoris, unspecified”). In some embodiments, if one of the set of facts collected from the patient encounter includes a general-level code such as ICD-10 I20, fact review component 106 may be programmed to automatically query the user as to whether one of the corresponding specific-level codes could be ascertained from the patient encounter instead. In some embodiments, fact review component 106 may present the user with a structured choice among the available specific-level codes, and may allow the user to choose among the available options.

In another example, fact review component 106 may be programmed to alert the user when a specific fact may be implied by the combination of two or more facts appearing together in the set of facts collected from the patient encounter. One example is a set of facts that included a diagnosis of pneumonia as well as a test result indicating that pseudomonas was found in a sputum culture. Based on a deterministic rule, or a statistical model result, indicating that these two facts in combination may imply a more specific form of pneumonia due to the presence of an organism, fact review component 106 may query the user as to whether the more specific diagnosis can be ascertained from the patient encounter.

In some embodiments, an alert that would otherwise be generated from the current patient encounter may be suppressed if there is information in the patient's medical history that already provides the additional specificity. To this end, in some embodiments fact review component 106 may have access to a data set of patient history records 160 for patient 122, and may query patient history records 160 for such information prior to generating an alert to the user. For example, if the set of facts from the current patient encounter specifies a condition but does not specify whether it is “acute” or “chronic”, but a previous record in patient history records 160 already specifies that the condition is “chronic”, then fact review component 106 in some embodiments may automatically edit the set of facts for the current patient encounter to specify that the condition is “chronic”, without bothering the user with an alert. However, in some embodiments, even if fact review component 106 can obtain such specificity enhancing information automatically, a message may still be generated to inform the user that the information is being automatically added, and to allow the user to reject the change if desired, or to ask the user to approve of the change being made.

In some embodiments, if it is a user 150, and not clinician 122, who responds to an alert to increase the specificity of a set of clinical facts for a patient encounter, clinician 120 may be prompted to approve any additional information provided by the other user 150 prior to finally approving the set of facts for the patient encounter. For example, in some embodiments user 150 may be a coding specialist who is assigned the task of reviewing and editing the set of clinical facts (which may include billing codes) into a version fit to be incorporated into an electronic medical record, patient reports, order forms, or other document types. In such a “back-end” arrangement, the set of clinical facts settled upon by coding specialist 150 may then in some embodiments be transmitted to clinician 120 to give final approval to the set of facts. In some other embodiments, coding specialist 150 may not be required. For example, in a “front-end” arrangement, clinician 120 may review and possibly edit the set of clinical facts himself, and finally approve the set of facts when he is satisfied. This may occur during the patient encounter in some embodiments, or at some time thereafter (e.g., before clinician 120 finally approves or signs off on the report) in other embodiments. In either type of arrangement, in some embodiments, processing by fact review component 106 or any other component to provide alerts, decision support, workflow tools or the like in relation to the set of facts may be performed prior to the clinician's final approval of the set of facts.

In some embodiments, similar processing may be performed by fact review component 106 to alert the user when it is determined that an unspecified diagnosis may possibly be ascertained from the patient encounter. As discussed above, examples of such unspecified diagnoses include comorbidities of one or more already specified diagnoses, and identification of one or more already specified diagnoses as complications of one or more other specified diagnoses and/or procedures. For example, if the set of facts collected for the patient encounter specified a diagnosis of pneumonia, and the patient's oxygen saturation is also low, it may be determined that respiratory failure, a comorbidity of pneumonia, may possibly be ascertained from the patient encounter. In such a case, fact review component 106 may generate an alert to the user. In some embodiments, such determinations may be made based on knowledge of best practices, with deterministic rules providing reminders of diagnoses that should be investigated, for best quality of care, when other related conditions are present. In other embodiments, such determinations may be made statistically, by inputting the collected set of facts and/or facts from the patient's medical history to a statistical model trained on past clinical reports and/or medical literature. In this way, patterns of diagnoses that tend to be related may be identified statistically, and alerts may be generated based on the likelihood that relationships observed in the past will surface in the current patient encounter. To this end, in some embodiments, fact review component 106 may have access to a data set of medical literature/documents 170 (such as past clinical reports from the healthcare institution and/or from other sources) from which statistical models may be built and updated.

In some embodiments, as discussed above, fact review component 106 may be programmed to generate an alert when it determines that two or more of the facts in the set collected from the patient encounter conflict with each other in some way, or when it determines that one or more of the facts in the set conflict with one or more facts in patient history records 160. In some embodiments, fact review component 106 may be programmed to automatically generate such alerts based on a known set of combinations of facts that have undesirable interactions. For example, an alert may be generated when the set of facts indicate that patient 122 has been prescribed a certain medication (drug A) in addition to a certain other medication (drug B) with which it negatively interacts, such that the two medications should not be prescribed together. In some embodiments, the prescriptions of both drug A and drug B may be specified in the set of facts collected from the current patient encounter, while in other embodiments, the prescription of drug A may be specified in a fact from the current patient encounter, and the prescription of drug B may be specified in a fact contained in patient history records 160. In some embodiments the known set of undesirable interactions may be represented in a data set locally accessible to fact review component 106, while in other embodiments, fact review component 106 may query one or more external data sets (such as those maintained by pharmacies) to determine whether given facts for patient 122 demonstrate any contraindications. In some embodiments, fact review component 106 or another suitable processing component may both maintain an internal data set and also query external data sets, for instance for periodic updates to the internal data set.

In some embodiments, an alert to a conflict may be triggered by a combination of facts, at least one of which does not correspond to a medication. For example, fact review component 106 may generate alerts for contraindications related to a combination of a medication with an allergy, a medication with a diagnosis, a medication with a patient's age or gender, a medication with a condition indicated in the patient's history, a medical procedure with any of the foregoing characteristics, or any other combination of a planned treatment with another clinical fact from the current patient encounter or from the patient's history for which the planned treatment is known to be contraindicated.

In some embodiments, as discussed above, fact review component 106 may generate an alert when it determines that there is an opportunity to add to the clinical documentation of the patient encounter for quality review purposes. In some embodiments, fact review component 106 may be programmed with a set of deterministic rules to generate automatic alerts in response to certain facts or certain combinations of facts, based on a standard set of quality of care measures. Such a quality of care standard may be proprietary and unique to the specific healthcare institution or may be a standard that is not institution specific, such as the PQRI standard or the JCAHO standard. Any suitable quality of care standard may be used, as aspects of the present invention are not limited to any particular quality of care standard. In some embodiments, when a collected fact or combination of facts is associated with a certain recommended action on the part of the clinician according to the quality of care standard, an alert may be provided to query the user as to whether the recommended action was performed. For example, if the set of facts specify that patient 122 is a smoker, in some embodiments fact review component 106 may generate an alert to remind clinician 120 to counsel patient 122 about quitting smoking, and to document the counseling in the patient record. In another example, if the set of facts specify that patient 122 presented with a heart attack, in some embodiments fact review component 106 may prompt clinician 120 to document how quickly aspirin was prescribed and/or administered, such that proof of compliance with the applicable quality of care standards may be documented. In some embodiments, fact review component 106 may be used to generate PQRI score reports, or the like, to send to insurance companies as compliance evidence to support reimbursement.

In some embodiments, as discussed above, fact review component 106 or another suitable component may generate an alert to the user when it determines that disambiguation is desired between multiple facts that could potentially be extracted from the same portion of the text narrative. For example, a term in the free-form narration might be linked to two different concepts in the formal ontology used by fact extraction component 104, and it might not be likely that both of those concepts were intended to coexist in the free-form narration. For example, if the text narrative contains the word “cold”, it may be difficult in some cases for fact extraction component 104 to determine whether clinician 120 intended that word to mean that patient 122 is cold to the touch, that patient 122 has a runny nose, or that patient 122 has chronic obstructive lung disease (COLD). In other examples, as discussed above, multiple alternative hypotheses for a fact to be extracted from a portion of the text may be identified, e.g., as the text is processed by one or more statistical fact extraction models. In such situations, fact review component 106 in some embodiments may provide a structured choice to the user to disambiguate between multiple facts tentatively extracted by fact extraction component 104. In some embodiments, each of the options provided in the structured choice may correspond to one of the multiple tentative facts, and the user may choose one of the options to specify which fact should actually be extracted from the free-form narration. As discussed above, if the user choosing among the facts is a person other than clinician 120, such as coding specialist 150, then in some embodiments clinician 120 may be prompted to approve the user's choice before finally approving the set of facts for the patient encounter. In other embodiments, the user may be prompted to provide disambiguating information in free-form, rather than as a structured choice, as aspects of the invention relating to prompting for disambiguating information are not limited to any particular implementation.

In various situations, as discussed above, fact review component 106 may be programmed to generate an alert including a structured choice among a number of options corresponding to medical facts that could possibly be ascertained from the patient encounter. Such a structured choice could include a choice among facts that could add specificity to a set of clinical facts already collected for the patient encounter, a choice among facts potentially implied by one or more combinations of facts already collected for the patient encounter, a choice to disambiguate between facts, or any other choice in which one or more structured options are presented to the user, from which the user may choose. Such a structured choice may be provided in any suitable way, including as a visual and/or audio listing of the options in the structured choice, as aspects of the invention are not limited in this respect. Similarly, the user's selection of an option from the structured choice may be received in any suitable way, including as manual input and/or spoken input, as aspects of the invention are not limited in this respect.

In some embodiments, in response to the user's selection of one of the options, fact review component 106 may, for example through use of fact extraction component 104, perform an update to the text narrative to make it explicitly state information corresponding to the selected fact. For example, in some embodiments, fact extraction component 104 may in a sense work backward from the selected fact to generate natural language text from which that fact could have been extracted in the forward sense. In some embodiments, the generated text may then be added to the text narrative. When the fact selected by the user through the structured choice is a replacement for or a disambiguation of a fact already extracted from the text narrative, the generated text may in some embodiments be used to replace the portion of the text narrative from which the original fact was extracted. In some embodiments, to determine where in the text narrative to add the generated text when no other text is to be replaced, fact extraction component 104 may again work backward based on how the selected fact would have been extracted from the narrative. For example, in some embodiments fact extraction component 104 may identify a section heading in the text narrative corresponding to the selected fact, and the generated text may be added to that section. (e.g., because a selected fact with a status of “history” would have been extracted from a section with a “history” heading, the corresponding generated text may be added to such a section in the text narrative.) In other embodiments, generated text may simply be added to a predetermined location in the text narrative, such as at the beginning or end of the narrative, regardless of the semantic content of the generated text.

In some embodiments, fact review component 106 may allow the user to specify a location in the text narrative where the generated text should be inserted, or may allow the user to correct the location initially determined automatically. In some embodiments, fact extraction component 104 or another suitable component may be used to update the generated text in response to the user's indication of a new location at which to insert it in the text narrative. For example, based on whether the user selects a location that is sentence-initial, sentence-medial or sentence-final, or a location that is its own sentence or is within another sentence, the generated text may be adjusted in terms of capitalization, spacing, punctuation, etc., to fit the selected location syntactically. In another example, if a selected fact specifies a family history of a certain condition, the gender of one or more pronouns within the generated text may be adjusted based on whether the user selects a location in a sentence about a female relative or about a male relative. As in other situations, if the user selecting an option from a structured choice and/or specifying a location in the text narrative is a person other than clinician 120, in some embodiments clinician 120 may be prompted to approve the user's selections prior to finally approving the set of clinical facts.

FIG. 6 illustrates a process for processing a free-form narration in accordance with some embodiments described herein. Initially, in act 610, a text is received that includes a free-form narration documenting a patient encounter.

In act 620, one or more clinical facts are extracted that correspond to an orderable item, by using an NLU engine implemented by one or more processors. In act 630, a determination is made as to whether the one or more clinical facts indicate an intent to order the orderable item. When it is determined that they do not, the process terminates. Alternatively, when it is determined that the one or more facts indicate an intent to order the orderable item, the process proceeds to act 640, wherein an order is generated for the actionable item.

While the embodiment in FIG. 6 terminates when it is determined that the one or more clinical facts do not indicate an intent to order the orderable item(s), in other embodiments actions can be taken to capture (e.g., by recording in the patient record) the extracted clinical fact(s), for example by noting that a patient is already taking a current medication.

FIG. 7 is a block diagram of a system in accordance with some embodiments described herein. It includes a source of free-form narrations of clinical encounters 701. As discussed above, the source can take any of numerous forms, including an ASR engine 102 of the type shown in FIG. 1, any type of computer storage medium that stores previously generated narrations, or any other source, as the aspects of the present invention described herein are not limited in any way by the source of the free-form clinical narrations. The free-form clinical narrations are operated upon by a fact extraction component 703 which can be implemented in any of the ways discussed above (including having one or more processors that implement one or more NLU engines) to extract one or more clinical facts from a free-form narration. When one or more of the extracted clinical facts corresponds to a mention of an orderable item, the fact extraction component can distinguish between whether the clinical fact indicates an intent to order the orderable item or not. When it is determined that an intent to order the orderable item is expressed in the free-form narration, the fact extraction component communicates with an order generation component 705 to generate an order for the orderable item. The order generation component may be coupled to a user interface 707, which may take any form and may be a user interface dedicated to the order generation component 705, or may be shared with other aspects of the system (e.g., the user interface may be shared with the user interface 140 described in FIG. 1). In some embodiments, the user interface may provide the user the capability of confirming any orders generated by the order generation component. Once an order is finalized, it may be sent to any of numerous order fulfillment systems 709 a-709 x, examples of which are described herein.

It should be appreciated that the various components and systems illustrated in FIG. 7 may be coupled in any suitable manner, and may be components that are located on the same physical computing system(s) or separate physical computing systems that can be coupled in any suitable way, including using any type of network, examples of which include a local network and a wide area network.

FIG. 8 is an example of a screenshot that may be used by the user interface 707 in providing a user with information about a generated order, and to allow the user to approve and submit the order. It should be appreciated that the information provided in the example of FIG. 8 is merely illustrative, as the information provided to a user can take any suitable form, and will vary depending upon the nature of the generated order. In the example of FIG. 8, a field 801 provides the name of the patient, a field 803 provides a sex of the patient, and a field 805 provides a date on which the order was created. In field 807, an order type is specified. In the example shown in FIG. 8, the order is a prescription for medication. Given that, the information provided to the user can include any desired information relating to a medication. In the example illustrated in FIG. 8, this information includes a field 809 for the name of the medication, a field 811 for the dosage, a field 813 for the route and a field 815 for the duration for which the medication is prescribed. Again, this is merely illustrative, as the information provided to the user can take any suitable form. In accordance with one embodiment of the invention, the fields 809-815 are editable by the user. In accordance with such embodiments, the user may be required to authenticate his/her identity and credentials to be authorized to edit the information in the order. In alternate embodiments, these fields are not editable, and the user only has the capability to either authorize or cancel the order. In this respect, as shown in FIG. 8, selectable item 817 is provided that, when selected by the user in any suitable way, authorizes the order and sends it to the order fulfillment system. Conversely, when the user selects item 819, the generated order is cancelled. It should be appreciated that the selectable items 817 and 819 can take any suitable form and be selected in any suitable manner, as the aspects of the present invention described herein are not limited in this respect.

It should be appreciated from the foregoing that another embodiment of the invention is directed to a method 900 for formatting text for clinical fact extraction, as illustrated in FIG. 9. Method 900 may be performed, for example, by one or more components of a fact review system such as ASR engine 102 and/or fact extraction component 104, although other implementations are possible as method 900 is not limited in this respect. Method 900 begins at act 910, at which an original text narrative (e.g., a textual representation of a narration of a patient encounter provided by a clinician) may be received. At act 920, the original text may be re-formatted to produce a formatted text narrative. At act 930, one or more clinical facts may be extracted from the formatted text. Method 900 ends at act 940, at which a linkage between at least one of the clinical facts and a corresponding portion of the original text may be maintained.

It should be appreciated from the foregoing that another embodiment of the invention is directed to a method 1000 for linking extracted clinical facts to text, as illustrated in FIG. 10. Method 1000 may be performed, for example, by one or more components of a fact review system such as fact extraction component 104 and/or fact review component 106, although other implementations are possible and method 1000 is not limited in this respect. Method 1000 begins at act 1010, at which a plurality of facts may be extracted from a free-form narration of a patient encounter provided by a clinician. At act 1020, a linkage may be maintained between each fact (or at least two of the facts) and the corresponding portion of the free-form narration from which it was extracted. Method 1000 ends at act 1030, at which a different indicator may be provided for each fact, to indicate the linkage between that fact and its corresponding portion of the free-form narration.

It should be appreciated from the foregoing that another embodiment of the invention is directed to a method 1100 for analyzing specificity in clinical documentation, as illustrated in FIG. 11. Method 1100 may be performed, for example, by one or more components of a fact review system such as ASR engine 102, fact extraction component 104 and/or fact review component 106, although other implementations are possible and method 1100 is not limited in this respect. Method 1100 begins at act 1110, at which a set of one or more clinical facts may be collected from a clinician's encounter with a patient. At act 1120, it may be determined from the set of facts that additional specificity may possibly be ascertained from the patient encounter. Method 1100 ends at act 1130, at which a user may be alerted that an additional fact adding specificity to the set of facts may possibly be ascertained from the patient encounter.

It should be appreciated from the foregoing that another embodiment of the invention is directed to a method 1200 for identifying unspecified diagnoses in clinical documentation, as illustrated in FIG. 12. Method 1200 may be performed, for example, by one or more components of a fact review system such as ASR engine 102, fact extraction component 104 and/or fact review component 106, although other implementations are possible and method 1200 is not limited in this respect. Method 1200 begins at act 1210, at which a set of one or more clinical facts may be collected from a clinician's encounter with a patient. At act 1220, it may be determined from the set of facts that an unspecified diagnosis may possibly be ascertained from the patient encounter. Method 1200 ends at act 1230, at which a user may be alerted that the unspecified diagnosis may possibly be ascertained from the patient encounter.

It should be appreciated from the foregoing that another embodiment of the invention is directed to a method 1300 for updating text in clinical documentation, as illustrated in FIG. 13. Method 1300 may be performed, for example, by one or more components of a fact review system such as fact extraction component 104 and/or fact review component 106, although other implementations are possible and method 1300 is not limited in this respect. Method 1300 begins at act 1310, at which one or more options may be provided to a user, the one or more options corresponding to one or more clinical facts that could possibly be ascertained from a patient encounter. At act 1320, a user selection of one of the options may be received. Method 1300 ends at act 1330, at which a text narrative (e.g., a textual representation of a free-form narration of the patient encounter provided by a clinician) may be updated to identify the fact corresponding to the selected option as having been ascertained from the patient encounter.

A medical documentation system in accordance with the techniques described herein may take any suitable form, as aspects of the present invention are not limited in this respect. An illustrative implementation of a computer system 1400 that may be used in connection with some embodiments of the present invention is shown in FIG. 14. One or more computer systems such as computer system 1400 may be used to implement any of the functionality described above. The computer system 1400 may include one or more processors 1410 and one or more tangible, non-transitory computer-readable storage media (e.g., volatile storage 1420 and one or more non-volatile storage media 1430, which may be formed of any suitable non-volatile data storage media). The processor 1410 may control writing data to and reading data from the volatile storage 1420 and the non-volatile storage device 1430 in any suitable manner, as the aspects of the present invention are not limited in this respect. To perform any of the functionality described herein, the processor 1410 may execute one or more instructions stored in one or more computer-readable storage media (e.g., volatile storage 1420), which may serve as tangible, non-transitory computer-readable storage media storing instructions for execution by the processor 1410.

The above-described embodiments of the present invention can be implemented in any of numerous ways. For example, the embodiments may be implemented using hardware, software or a combination thereof. When implemented in software, the software code can be executed on any suitable processor or collection of processors, whether provided in a single computer or distributed among multiple computers. It should be appreciated that any component or collection of components that perform the functions described above can be generically considered as one or more controllers that control the above-discussed functions. The one or more controllers can be implemented in numerous ways, such as with dedicated hardware, or with general purpose hardware (e.g., one or more processors) that is programmed using microcode or software to perform the functions recited above.

In this respect, it should be appreciated that one implementation of embodiments of the present invention comprises at least one computer-readable storage medium (i.e., a tangible, non-transitory computer-readable medium, such as a computer memory, a floppy disk, a compact disk, a magnetic tape, or other tangible, non-transitory computer-readable medium) encoded with a computer program (i.e., a plurality of instructions), which, when executed on one or more processors, performs above-discussed functions of embodiments of the present invention. The computer-readable storage medium can be transportable such that the program stored thereon can be loaded onto any computer resource to implement aspects of the present invention discussed herein. In addition, it should be appreciated that the reference to a computer program which, when executed, performs any of the above-discussed functions, is not limited to an application program running on a host computer. Rather, the term “computer program” is used herein in a generic sense to reference any type of computer code (e.g., software or microcode) that can be employed to program one or more processors to implement above-discussed aspects of the present invention.

The phraseology and terminology used herein is for the purpose of description and should not be regarded as limiting. The use of “including,” “comprising,” “having,” “containing”, “involving”, and variations thereof, is meant to encompass the items listed thereafter and additional items. Use of ordinal terms such as “first,” “second,” “third,” etc., in the claims to modify a claim element does not by itself connote any priority, precedence, or order of one claim element over another or the temporal order in which acts of a method are performed. Ordinal terms are used merely as labels to distinguish one claim element having a certain name from another element having a same name (but for use of the ordinal term), to distinguish the claim elements from each other.

Having described several embodiments of the invention in detail, various modifications and improvements will readily occur to those skilled in the art. Such modifications and improvements are intended to be within the spirit and scope of the invention. Accordingly, the foregoing description is by way of example only, and is not intended as limiting. The invention is limited only as defined by the following claims and the equivalents thereto. 

What is claimed is:
 1. A method comprising: extracting from a free-form input regarding an encounter with a patient by a clinician, using a natural language understanding engine implemented by one or more processors, at least one clinical fact corresponding to a mention in the free-form input of an orderable item; determining, based at least in part on the at least one clinical fact extracted from the free-form input using the natural language understanding engine, whether the mention of the orderable item in the free-form input indicates an intent to order the orderable item or does not indicate an intent to order the orderable item; in response to determining that the mention of the orderable item in the free-form input indicates an intent to order the orderable item, generating an order for the orderable item; and in response to determining that the mention of the orderable item in the free-form input does not indicate an intent to order the orderable item, refraining from generating the order for the orderable item.
 2. The method of claim 1, wherein the extracting comprises extracting at least one clinical fact corresponding to a mention of an orderable item selected from the group consisting of: a medication order, a procedure order, a lab order, a diagnostic test order, an appointment order, a referral order, and a communication order.
 3. The method of claim 1, further comprising identifying a set of information fields for generating the order for the orderable item.
 4. The method of claim 3, further comprising identifying one or more items of missing information, for the set of information fields, that are not included in the at least one clinical fact extracted from the free-form input.
 5. The method of claim 4, further comprising: prompting the clinician to supply at least one of the one or more missing items of information; and/or inferring at least one of the one or more missing items of information from documentation of the patient's history.
 6. The method of claim 1, wherein generating the order for the orderable item comprises: identifying a target computerized system for fulfilling the generated order; conforming the generated order to a standard appropriate for the target computerized system for fulfilling the order; and transmitting the conformed order to the target computerized system.
 7. The method of claim 1, further comprising: in response to a determination there are one or more conflicts between the orderable item and one or more other facts extracted from the free-form input and/or from the patient's history, alerting the clinician to the one or more conflicts.
 8. The method of claim 1, further comprising: receiving audio of the free-form input, the audio comprising sound of at least the clinician speaking.
 9. The method of claim 8, wherein receiving the audio of the free-form input comprises receiving the audio during the encounter.
 10. The method of claim 8, wherein receiving the audio of the free-form input comprises receiving speech of a free-form narration regarding the encounter with the patient by the clinician.
 11. The method of claim 10, wherein receiving speech of a free-form narration comprises receiving speech of the clinician dictating the free-form narration.
 12. The method of claim 1, wherein determining whether the mention indicates an intent to order the orderable item or does not indicate an intent to order the orderable item comprises determining whether the at least one clinical fact indicates that the mention of the orderable item appears in context of the clinician stating that the clinician intends to order the orderable item.
 13. Apparatus comprising: at least one processor; and at least one processor-readable storage medium storing processor-executable instructions that, when executed by the at least one processor, cause the at least one processor to perform a method comprising: extracting from a free-form input regarding an encounter with a patient by a clinician, using a natural language understanding engine implemented by the at least one processor, at least one clinical fact corresponding to a mention in the free-form input of an orderable item; determining, based at least in part on the at least one clinical fact extracted from the free-form input using the natural language understanding engine, whether the mention of the orderable item in the free-form input indicates an intent to order the orderable item or does not indicate an intent to order the orderable item; in response to determining that the mention of the orderable item in the free-form input indicates an intent to order the orderable item, generating an order for the orderable item; and in response to determining that the mention of the orderable item in the free-form input does not indicate an intent to order the orderable item, refraining from generating the order for the orderable item.
 14. The apparatus of claim 13, wherein the method further comprises: identifying a set of information fields for generating the order for the orderable item; and identifying one or more missing items of information for the set of information fields, that are not included in the at least one clinical fact extracted from the free-form input.
 15. The apparatus of claim 14, wherein the method further comprises: prompting the clinician to supply at least one of the one or more missing items of information; and/or inferring at least one of the one or more missing items of information from documentation of the patient's history.
 16. At least one non-transitory computer-readable storage medium encoded with computer-executable instructions that, when executed, perform a method comprising: extracting from input received regarding an interaction of a patient and a clinician, using natural language understanding, at least one clinical fact corresponding to a mention of an orderable item in the input; determining, based on the at least one clinical fact extracted from the input using the natural language understanding, whether the mention of the orderable item in the input appears in context of an intent to order the orderable item or not in context of an intent to order the orderable item; in response to determining that the mention of the orderable item in the input appears in context of intent to order the orderable item, generating an order for the orderable item; and in response to determining that the mention of the orderable item in the input does not appear in context of intent to order the orderable item, refraining from generating the order for the orderable item.
 17. The at least one computer-readable storage medium of claim 16, wherein the method further comprises identifying a set of information fields for generating the order for the orderable item.
 18. The at least one computer-readable storage medium of claim 17, wherein the method further comprises: based at least in part on processing the at least one clinical fact and the set of information fields, identifying one or more missing items of information for the set of information fields that were not extracted from the input; and prompting the clinician to supply at least one of the one or more missing items of information and/or inferring at least one of the one or more missing items of information from documentation of the patient's history.
 19. The at least one non-transitory computer-readable storage medium of claim 16, wherein extracting the at least one clinical fact from the input received regarding the interaction of the patient and the clinician comprises processing audio for the interaction, the audio comprising sound of at least the clinician speaking.
 20. The at least one non-transitory computer-readable storage medium of claim 19, wherein the method further comprises receiving the audio for the interaction during the interaction of the patient and the clinician. 